Adds a bunch of flexability around egress #1019
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
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.
In the event that a pod is on multiple networks we may have a scenario where we don't want to egress to that network.
If we want to ensure we don't egress for a CIDR we can add to the service the following:
kube-vip.io/egress-denied-networks:172.18.0.0/24These are comma separated values, so we we can add multiple networks not to egress.
Additionally if we want to egress to only certain networks we can do the following:
kube-vip.io/egress-allowed-networks:172.18.0.0/24(I've also moved all of the testing about a bit to make this easier to test)