Fix bug in kube-proxy of not updating iptables rules if a service's public IPs change#6123
Merged
Merged
Conversation
Contributor
Author
|
Updated based on suggestion in #6061. |
Member
There was a problem hiding this comment.
Probably don't need TCP and UDP - this has nothing to do with ports, rigth?
Contributor
Author
There was a problem hiding this comment.
Right, good point. Removed.
public IPs change, and add tests to catch the bug.
thockin
added a commit
that referenced
this pull request
Mar 30, 2015
Fix bug in kube-proxy of not updating iptables rules if a service's public IPs change
|
Thanks Tim. Sorry - I just noticed this now :-( |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
And add tests to catch the bug. Ran into this while testing #5180.