Skip to content
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

Removing microk8s snap doesn't kill calico-node #2824

Closed
MrMYHuang opened this issue Jan 10, 2022 · 2 comments
Closed

Removing microk8s snap doesn't kill calico-node #2824

MrMYHuang opened this issue Jan 10, 2022 · 2 comments
Labels

Comments

@MrMYHuang
Copy link

MrMYHuang commented Jan 10, 2022

microk8s version: microk8s (1.22/stable) v1.22.4

Steps to reproduce the bug:

sudo snap install microk8s --classic
microk8s kubectl get pod -A --watch

Then, wait until calico-node is ready.

Then, run sudo snap remove microk8s. You will find calico-node still run by ps aux|grep calico-node.

myh@alston-ubuntu:~$ ps aux|grep calico-node
root     1212222  5.1  0.1 1953788 58432 ?       Sl   14:07   0:14 calico-node -felix

It continues generating iptables-legacy rules (even if do flush rules and delete chains) and breaks cilium L7 policy functions (see cilium/cilium#18350 (comment)).

A workaround is killing calico-node manually.

@stale
Copy link

stale bot commented Dec 6, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Dec 6, 2022
@stale stale bot closed this as completed Jan 5, 2023
@sbe-arg
Copy link

sbe-arg commented Jul 31, 2024

This issue is very annoying...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants