Default network Policy and extraObjects #350
Open
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
jehutyy
requested review from
hors,
tplavcic,
nmarukovich,
ptankov,
jvpasinatto and
eleo007
as code owners
|
|
…amespace and between psmdb namespace and percona-mongodb operator's namespace.
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.
The actual chart overlook network policy thus leading to mongo database not being able to reconcile within an environment that uses network policies.
I introduce two netpol : one which allows intra-namespace communication and another one that allows communication between db namespace and operator namespace.
Additionally, there's an extraObjects value that can be used when a use case isn't covered by available values in values file.