-
Notifications
You must be signed in to change notification settings - Fork 717
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
migrate users away from CRI socket paths that don't have URL scheme #2426
Comments
kubernetes/kubernetes#100578 is not handling the |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
/remove-lifecycle stale |
Testing 1.22, and I find
I got the error when I upgrade from v1.22.0-beta.1 to v1.22.0 with kubelet 1.21.1. I will look into the problem here.(I am not familiar with the history of this annotation and need some digging)[One of my cluster node was wrongly removed by |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
i can try tacking the upgrade problem for 1.24 as part of the dockershim refactors. #2626
it might be a good idea to do this soon given the kubelet endpoint flag is no longer "experimental". |
updated PR is here: |
Is it too early in v1.26 for users to turn warnings into errors? |
1.27 sounds better but we might want to do it only after the kubelet starts doing it, if that ever happens. |
As a note for people (like me) who ended up at this issue via search engines, if your kubeadm'ed cluster is throwing this error when running
You can fix this by manually doing:
and in the
Make sure to verify this is the correct socket path (snoop a control plane node to see what they have set, or just use the same one you use for crictl on the command line on that given node). |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@pacoxu i think we can put that on hold until the kubelet decides to error out. or perhaps just wait for minumum one more release. |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
moved to "Next" milestone, lowered priority and frozen |
let's close this for now. in a future release if the kubelet drops support, we can start erroring on the kubeadm side before a kubelet is deployed. |
summary of the problem:
what we should do:
1.24 action items:
kubeadm: ensure CRI endpoints are managed with URL schemes kubernetes#107295
1.25 action items:
kubeadm: remove temporary handling of CRI socket paths without URL scheme kubernetes#109356
test/e2e_kubeadm: add URL scheme test for node CRI annotations kubernetes#110287
1.26
kubeadm: revert dedup prefix unix:// in node annotation kubernetes#112005
future release:
The text was updated successfully, but these errors were encountered: