-
Notifications
You must be signed in to change notification settings - Fork 208
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
install: don't delete the 'aws-node' DaemonSet #208
install: don't delete the 'aws-node' DaemonSet #208
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is very nice! 🚀
Could we test it by adding a check in the EKS workflows, to verify the aws-node DaemonSet's pods exists after Cilium is uninstalled? Or is it not worth it?
Hi @bmcustodio. Could you please rebase the PR branch against latest Also there's a review remark from @pchaigno which you might want to address, if feasible? |
Instead of deleting the 'aws-node' DaemonSet, which is permanent, we can be gentler and just evict its pods by setting a node selector that won't ever be matched (unless someone wants it to by explicitly setting the required label). This allows 'cilium uninstall' to gracefully revert the 'aws-node' DaemonSet to its previous state, as it might contain customizations that would otherwise be lost. Signed-off-by: Bruno Miguel Custódio <[email protected]>
b7af12c
to
7c26ae4
Compare
For some reason the GitHub actions weren't triggered when you pushed a new version. I'll close and re-open the PR hoping that this will trigger the tests. |
Seems to have worked 🎉 |
AKS failure is only due to the PR being opened from outside the cilium-cli repo. The code changes themselves only touch the EKS-specific jobs and codepaths so there should be no regression in the AKS job. Should be good to merge. |
Instead of deleting the
aws-node
DaemonSet, which is permanent, we can be gentler and just evict its pods by setting a node selector that won't ever be matched (unless someone wants it to by explicitly setting the required label on a node).This allows
cilium uninstall
to gracefully revert theaws-node
DaemonSet
to its previous state, as it might contain customizations that would otherwise be lost.