Open neopointer opened 5 days ago
This is by design. k0s stop
works similarly to kubelet / containerd. When these are stopped, containers continue to run. If you want to stop everything, you have to make sure that k0s doesn't start automatically after a reboot, and then restart the node. If you want to decommission the node, there's k0s reset
, which goes some extra steps to try to terminate everything But: it will also wipe k0s's data directory.
@twz123 in this case, this is not an issue, right? I would close it then.
Can we add this as documentation to k0s stop
's documentation at least?
Can we add this as documentation to k0s stop's documentation at least?
Sure, what do you have in mind? PRs welcome, too 🙃
Before creating an issue, make sure you've checked the following:
Platform
Version
v1.31.2+k0s.0
Sysinfo
`k0s sysinfo`
What happened?
After stopping k0s via
k0s stop
, I still see several process running.I'm using Cilium, but I'm not sure if this has anything to do with it.
Steps to reproduce
I don't believe there are clear steps to reproduce, but try to use Cilium and see whether all processes stop.
Expected behavior
All processes related to k0s are gone after running
k0s stop
.Actual behavior
Multiple
containerd
process are still running after usingk0s stop
.Screenshots and logs
No response
Additional context
No response