Add support for X509 mutual authentication/authorization #4
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
helm install --dry-run
has been performed locallyPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Addresses feature request for X509 mutual authentication/authorization (Resolves #3)
What is the new behavior?
New configuration parameters added to allow kube-native use of the x509 mutual authentication/authorization provided by the database-agent and mongodb-audit-watcher
In addition this PR contains the following changes:
Does this introduce a breaking change?
There are no breaking changes as these features are only enabled if
<service>.mongoTLS.enabled
is set totrue
(which is not the default behaviour)Other information
All the environment variables that are used to control the new functionality are documented in the READMEs for each chart