This message was deleted.
# k3s
a
This message was deleted.
c
Yes, like the docs say - just replace the binary and restart the service.
you are welcome to drain first if you want. but you don’t have to.
Stopping containerd and/or the kubelet does not kill the pods that they started. This is always the case, regardless of Kubernetes distro.
l
Yeah, that lines up with what I have experienced elsewhere
Thank you @creamy-pencil-82913, I appreciate the confidence boost
c
if your pods can’t tolerate a short apiserver outage then you might want to drain. but usually things don’t care.
l
Good point, I could imagine a particular class of application caring, but we don't have anything quite so complex
c
containers keep running, container networking stays as it was last configured, and so on.
l
Excellent
Would it be silly if I proposed a clarifying comment to that ^ bit of docs just to make it clear to other people who aren't sure how that all works?
Then presumably you would never receive such a question again
c
sure if you think thats necessary.
l
I think it would be helpful for folks like me coming from the various hosted k8s offerings that don't really have this level of insight
I'll make a PR, see what you think
No pressure