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

talosctl health should not check kube-proxy when it is disabled #3299

Closed
bzub opened this issue Mar 14, 2021 · 0 comments · Fixed by #3315
Closed

talosctl health should not check kube-proxy when it is disabled #3299

bzub opened this issue Mar 14, 2021 · 0 comments · Fixed by #3315
Assignees
Milestone

Comments

@bzub
Copy link
Contributor

bzub commented Mar 14, 2021

Bug Report

Description

Running talosctl health when .cluster.proxy.disabled is true hangs checking for kube-proxy.

Logs

❯ talosctl --context tte-metal -n 10.87.64.11 health
discovered nodes: control plane: ["10.87.64.11"], worker: []
waiting for etcd to be healthy: ...
waiting for etcd to be healthy: OK
waiting for bootkube to finish: ...
waiting for bootkube to finish: OK
waiting for apid to be ready: ...
waiting for apid to be ready: OK
waiting for kubelet to be healthy: ...
waiting for kubelet to be healthy: OK
waiting for all nodes to finish boot sequence: ...
waiting for all nodes to finish boot sequence: OK
waiting for all k8s nodes to report: ...
waiting for all k8s nodes to report: OK
waiting for all k8s nodes to report ready: ...
waiting for all k8s nodes to report ready: OK
waiting for all control plane components to be ready: ...
waiting for all control plane components to be ready: OK
waiting for kube-proxy to report ready: ...
waiting for kube-proxy to report ready: no pods found for namespace "kube-system" and label "k8s-app=kube-proxy"
healthcheck error: rpc error: code = Unknown desc = context deadline exceeded

Environment

  • Talos version:
Client:
        Tag:         v0.9.0-beta.0
        SHA:         dbcb643e
        Built:
        Go version:  go1.15.8
        OS/Arch:     darwin/amd64

Server:
        NODE:        10.87.64.11
        Tag:         v0.9.0-beta.0
        SHA:         dbcb643e
        Built:
        Go version:  go1.15.8
        OS/Arch:     linux/amd64
  • Kubernetes version:
Client Version: v1.20.4
Server Version: v1.20.4
  • Platform: metal
@smira smira self-assigned this Mar 15, 2021
@smira smira added this to the v0.9 milestone Mar 15, 2021
@AlekSi AlekSi self-assigned this Mar 15, 2021
AlekSi added a commit to AlekSi/talos that referenced this issue Mar 16, 2021
Fixes siderolabs#3299.

Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
talos-bot pushed a commit to AlekSi/talos that referenced this issue Mar 16, 2021
Fixes siderolabs#3299.

Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
AlekSi added a commit to AlekSi/talos that referenced this issue Mar 16, 2021
Fixes siderolabs#3299.

Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
talos-bot pushed a commit that referenced this issue Mar 16, 2021
Fixes #3299.

Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
smira pushed a commit to smira/talos that referenced this issue Mar 17, 2021
Fixes siderolabs#3299.

Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
(cherry picked from commit 7662d03)
talos-bot pushed a commit that referenced this issue Mar 17, 2021
Fixes #3299.

Signed-off-by: Alexey Palazhchenko <alexey.palazhchenko@gmail.com>
(cherry picked from commit 7662d03)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 26, 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.

3 participants