-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Upgrading kubeadm clusters #36896
Comments
@Goutami-Gowda: This issue is currently awaiting triage. SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This issue sounds more like a request for support and less like an issue specifically for docs. I encourage you to bring your question to the You can also open issues for Kubernetes functionality in https://github.com/kubernetes/kubernetes or https://github.com/kubernetes/kubeadm. If this is a documentation issue, please re-open this issue. /kind support |
@mtardy: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
hello, I am trying to upgrade kubeadm cluster from 1.23.5 to 1.24.5. i am following this document https://v1-24.docs.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/.
after kubeadm upgrade. kubelet upgrade is giving me this error. i need help here.
kubelet upgrade Error: failed to parse kubelet flag: unknown flag: --network-plugin
and node is in not ready state.
this is the command i ran for kubectl drain since i have some stateful state.
kubectl drain dev1 --force=false --disable-eviction=true --ignore-daemonsets=true --delete-emptydir-data=false
The text was updated successfully, but these errors were encountered: