Fix iptables rules clean during upgrade #7591
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Roberto Bonafiglia <roberto.bonafiglia@suse.com>
brandond
approved these changes
May 22, 2023
galal-hussein
approved these changes
May 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Removed the CNI iptables rules clean when an upgrade is done.
Unlike rules managed by the kubelet and kube-router, CNI rules are only created when the pod starts. If we remove them in the install script, networking to existing pods (such portmap rules for nodePort pods) will be broken.
Types of Changes
Verification
Testing
Linked Issues
User-Facing Change
Further Comments