K8SPSMDB-997 - Add serviceAccountName to the existing resources #242
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
|
|
tplavcic
changed the title
|
@Rockawear Thank you very much for the contribution! Your commits were merged and are available in chart version 1.15.0. |
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 is to address issues encountered in the link below. Basically, PSMDBBackup aren't working when using
serviceAccountNamebecause the entire cluster is usingdefaultwhen using the psmdb-db chart. Since the crd supports serviceAccoountName already, this change adds the ability to setserviceAccountNameas needed. Ideally, we would want just the specific container to have this kind of access. After some research, it doesn't seem possible to container level service account.https://forums.percona.com/t/how-to-setup-aws-s3-storage-backup-using-service-account-irsa/21672