Closed
Conversation
Adds `VaultAuthBackend`, `VaultKubernetesAuthBackend` and `VaultKubernetesAuthBackendRole` CRDs, with corresponding controllers. These CRDs enable the management of Vault auth backends, along with kubernetes auth configs and roles through the operator.
|
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds
VaultAuthBackend,VaultKubernetesAuthBackendandVaultKubernetesAuthBackendRoleCRDs, with corresponding controllers.These CRDs enable the management of Vault auth backends, along with kubernetes auth configs and roles through the operator.
This is obviously a very rough PoC and more intended as a throwaway than anything else, but would be nice to get some feedback 😄 Tested this using a local k8s cluster and Vault cluster and these work fine so far.