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
worker node shutdown waits long for containerd-shim #1251
Comments
How long is long? :) I'd guess it's around 90sec which I remember is the systemd default |
but from users point of view: I have nothing running, so in my opinion a node should reboot/shut down fast |
The root cause is containerd shims not handling SIGTERM properly: containerd/containerd#5502 A fix upstream is targeted for containerd 1.6, there's not much we can do on k0s level before that ships out. |
The issue is marked as stale since no activity has been recorded in 30 days |
Remove stale, we're still waiting for upstream to have fix for this |
The containerd fix has been backported into 1.5.x recently (containerd/containerd#6509), so maybe there'll be a new release soon. |
There's now 1.6.0 containerd release which has this fix. We should bump main to use that. No release yet for 1.5.x that includes this fix. |
The issue is marked as stale since no activity has been recorded in 30 days |
asdf |
k0s v1.23.5+k0s.0 is out, shipping containerd 1.5.11, which has the fix. |
The issue is marked as stale since no activity has been recorded in 30 days |
Closing as I believe this is fixed as of v1.23.5+k0s.0. Please ping me if it's not working as intended. |
waits for containerd-shims:
(Ubuntu 20.04, running in proxmox vm, hence the screenshot)
The text was updated successfully, but these errors were encountered: