Added support to configure default vault namespace on the agent config #345
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.
At the moment the only option to configure vault enterprise namespace is through the annotation
vault.hashicorp.com/namespace
at Pod level.This presents some autonomy challenges for cluster/vault administrators. Example:
This PR adds the ability to define a default vault namespace on the agent config. If the vault namespace isn't defined at Pod, then the configured vault namespace will be used, otherwise the Pod annotation value is used