Issue #282: Migrate secret management from hashicorp vault to Azure Key Vault #291
Conversation
This file contains 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
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.
This pull request includes changes that migrate the secrets management from HashiCorp Vault to Azure Key Vault across various of our Kubernetes deployments. The modifications involve updating the SecretProviderClass resources to use
the Azure Key Vault provider and adjusting the environment variables and volume mounts in the deployment configurations to align with the new secrets setup. The changes ensure that secrets are now retrieved directly from
Azure Key Vault using the CSI driver, enhancing the integration with Azure-managed identities and streamlining the secrets management process.
TODO :