You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've installed microk8s from 1.29-strict/edge. I have not created any new pods. After running snap remove --purge microk8s, I see the following processes still running:
With some experimentation, I was able to confirm that if any pods are started before, they keep running even after snap remove. So a workaround I've added in snapd spread tests is to:
Thank you for raising this. This is currently a limitation with the strictly confined version of MicroK8s, and should not be a problem with the classic flavor.
Summary
I've installed microk8s from 1.29-strict/edge. I have not created any new pods. After running
snap remove --purge microk8s
, I see the following processes still running:With some experimentation, I was able to confirm that if any pods are started before, they keep running even after snap remove. So a workaround I've added in snapd spread tests is to:
What Should Happen Instead?
I believe those should be part of the snap
remove
hook, which is invoked when removing the last revision of microk8s in the system.Reproduction Steps
Can you suggest a fix?
The
remove
hooks is an appropriate place for cleaning up.The text was updated successfully, but these errors were encountered: