LIFO order for network policies #258
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
added 2 commits
October 11, 2018 12:31
sharmasushant
pushed a commit
to sharmasushant/azure-container-networking
that referenced
this pull request
Oct 24, 2018
* reverseOrder * add npm to circleCI
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.
What this PR does / why we need it:
This PR:
Changes the order of Azure-NPM for applying network policies from FIFO to LIFO.
As per @neumanndaniel suggested, kubernetes administrators/network operators usually apply a deny-all policy then whitelist certain traffic. Without this PR to achieve this, one would have to whitelist all traffic first then apply the deny-all policy.
Adds Azure-NPM to CircleCI config for CI/CD.
Which issue this PR fixes:
Fixes #217
Special notes for your reviewer:
This is a change of behavior, not a bug fix.