Store password in secret#63
Draft
polinashtanko wants to merge 4 commits into
Draft
Conversation
Contributor
|
@polinashtanko could you link in the MR description the related ticket and resolve the conficts? |
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.
Added passwordSecretRef field to mariadb, mongodb, postgres providers
Introduced new struct types: SecretKeyRef and PasswordSecretRef
Updated controllers to retrieve the password from the referenced Kubernetes Secret when passwordSecretRef is provided; otherwise, fallback to the existing plain string password field
Modified RBAC roles to include permissions for accessing Secrets (get, list, watch)
Updated CRD schema definitions to support the new passwordSecretRef field
Adjusted test suits to demonstrate usage of the secret reference
Ticket https://amazeeio.atlassian.net/browse/PLAT-548