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

fix an issue where the containerd health check failed on k8s 1.32 #5565

Merged
merged 3 commits into from
Feb 14, 2025

Conversation

laverya
Copy link
Member

@laverya laverya commented Feb 14, 2025

What this PR does / why we need it:

rerunning kurl installers in 1.32 failed with an error:

Error from server (Forbidden): nodes is forbidden: User "system:node:laverya-kurl-validation" cannot list resource "nodes" in API group "" at the cluster scope: node 'laverya-kurl-validation' cannot read all nodes, only its own Node object
spent 5m attempting to run "kubectl --kubeconfig=/etc/kubernetes/kubelet.conf get nodes.v1." without success

This is because the role for the /etc/kubernetes/kubelet.conf user now only has access to its own node

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?


Does this PR require documentation?

@laverya laverya requested a review from a team as a code owner February 14, 2025 18:49
@laverya laverya added type::bug Something isn't working bug::normal labels Feb 14, 2025
Copy link
Contributor

Copy link
Contributor

@laverya laverya merged commit c995a8e into main Feb 14, 2025
8 of 9 checks passed
@laverya laverya deleted the laverya/fix-containerd-health-check-on-k8s-132 branch February 14, 2025 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug::normal type::bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants