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
Static pod terminating status can not be bring back #22625
Comments
@kubernetes/sig-node |
@xinxiaogang Now kubelet ignores all modifications to the mirror pod as long as the annotation remains unchanged. There are more mirror pod related discussion in #16627, you can follow up if you are interested, :) However, I think what you suggested is reasonable somehow. @yujuhong except for the annotation change, if the |
Thanks @Random-Liu . I have a PR for the fix and it works in our cluster now. #22626 Actually, all of our static pods (etcd, apiserver, etc) are running well, but the problem of |
@xinxiaogang Thank you very much for the fix. :) We'll review it. |
@xinxiaogang, as a quick workaround, you can force delete the mirror pods (
Yes, we should do it. Ideally we should resolve the mirror pod issue #16627 altogether, but this seems like a relatively isolated fix.
Thanks for the PR! |
- During `kubelet` `syncPod`, check mirror pod `DeletionTimestamp` value to determine whether re-create mirror pod for running static pod.
If the mirror pod of static pod be deleted via apiserver, the mirror pod status would stuck at
Terminating
. Even restartingkubelet
does not work.kubelet
should sync the running static pod status to mirror pod.The text was updated successfully, but these errors were encountered: