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

Add vaultConnectionRef to the transit auth method and provide a default #201

Merged
merged 8 commits into from
May 24, 2023

Conversation

kschoche
Copy link
Contributor

@kschoche kschoche commented May 22, 2023

Adds manager.controller.clientCache.storageEncryption.vaultVonnectionRef to the values.yaml to be used by the default-transit-auth-method.
This defaults to default which uses the default VaultAuthMethod in the VSO namespace.

Fixes #196

Note to reviewers: The spec of the default transit auth method is currently missing support for other auth methods beyond kubernetes. I will circle back to add that support once a couple more auth methods have landed.

@kschoche kschoche added this to the v0.1.0-beta.1 milestone May 22, 2023
@kschoche kschoche self-assigned this May 22, 2023
@kschoche kschoche requested a review from a team May 22, 2023 18:25
@kschoche kschoche merged commit b9d4f2f into main May 24, 2023
@kschoche kschoche deleted the VAULT-16409/add_vaultConnection_to_transitAuthMethod branch May 24, 2023 01:40
gautambaghel pushed a commit that referenced this pull request May 26, 2023
…lt (#201)

* Add vaultConnectionRef to the transit auth method and provide a default

* remove extra unit test bits

* test

* remove debug code

* set default explicitly in values.yaml

* Add a changelog entry + sign commit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vaultConnectionRef not set vault-secrets-operator-default-transit-auth
3 participants