Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restrict Operator to Vault Namespace #246

Merged
merged 1 commit into from
Jan 15, 2024

Conversation

ricoberger
Copy link
Owner

It is now possible to restrict the operator to a specific Vault Namespace. When the VAULT_RESTRICT_NAMESPACE environment variable is set to true the operator only reconciles secrets where the spec.vaultNamespace field is the same as the VAULT_NAMESPACE environment variable. VaultSecrets with another spec.vaultNamespace value will be ignored.

When this feature is enabled the operator can not be used with nested Vault Namespaces.

Closes #234

It is now possible to restrict the operator to a specific Vault
Namespace. When the `VAULT_RESTRICT_NAMESPACE` environment variable is
set to `true` the operator only reconciles secrets where the
`spec.vaultNamespace` field is the same as the `VAULT_NAMESPACE`
environment variable. VaultSecrets with another `spec.vaultNamespace`
value will be ignored.

When this feature is enabled the operator can not be used with nested
Vault Namespaces.
@ricoberger ricoberger added the changelog: added A new feature was added label Jan 15, 2024
@ricoberger ricoberger merged commit 1f77927 into main Jan 15, 2024
7 checks passed
@ricoberger ricoberger deleted the restrict-operator-to-vault-namespace branch January 15, 2024 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog: added A new feature was added
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exclude given VaultSecrets
1 participant