Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Talos endpoints in kubernetes #6566

Closed
sergelogvinov opened this issue Nov 29, 2022 · 0 comments · Fixed by #6580
Closed

Talos endpoints in kubernetes #6566

sergelogvinov opened this issue Nov 29, 2022 · 0 comments · Fixed by #6580
Assignees
Milestone

Comments

@sergelogvinov
Copy link
Contributor

Bug Report

Talos client uses domain name talos.default.svc in kubernetes deployments.
If client cannot connect to the talos-api, it will fall.

talos.default.svc endpoints has all IPs of the control-plane. I think some of them do not accessible from the kubetrnetes subnets.

Logs

W1129 12:42:28.666200       1 logging.go:59] [core] [Channel #1 SubChannel #2] grpc: addrConn.createTransport failed to connect to {
  "Addr": "172.16.0.11:50000",
  "ServerName": "172.16.0.11:50000",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "transport: Error while dialing dial tcp 172.16.0.11:50000: i/o timeout"
F1129 12:42:28.666567       1 main.go:98] Cloud provider could not be initialized: could not init cloud provider "talos": failed to initialized talos client: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp 172.16.0.11:50000: i/o timeout"

Environment

  • Talos version: master
  • Kubernetes version: [kubectl version --short]
  • Platform:
@sergelogvinov sergelogvinov changed the title Talos endpoints in kubernetes filter Talos endpoints in kubernetes Nov 29, 2022
@smira smira added this to the v1.3 milestone Nov 30, 2022
@smira smira self-assigned this Dec 2, 2022
smira added a commit to smira/talos that referenced this issue Dec 2, 2022
Fixes siderolabs#6566

This avoid putting all node addresses which might not be routeable
across Kubernetes.

Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
smira added a commit to smira/talos that referenced this issue Dec 2, 2022
Fixes siderolabs#6566

This avoid putting all node addresses which might not be routeable
across Kubernetes.

Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
smira added a commit to smira/talos that referenced this issue Dec 7, 2022
Fixes siderolabs#6566

This avoid putting all node addresses which might not be routeable
across Kubernetes.

Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
(cherry picked from commit 0219d11)
DJAlPee pushed a commit to DJAlPee/talos that referenced this issue May 22, 2023
Fixes siderolabs#6566

This avoid putting all node addresses which might not be routeable
across Kubernetes.

Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants