-
Notifications
You must be signed in to change notification settings - Fork 118
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 support for existing backup credentials #197
Comments
I was just about to set up my first cluster and ran into that problem as well. Since we are using GitOps, it's anything but ideal to store the secret access key straight in Git. |
Same here. I can not store the secret in the values file. |
Hi all, any update about this feature? |
@SalvoRusso8 There is PR that implements this: #239. Would you be able to test that and confirm it works? |
Currently, the cluster chart create a secret containing backup credentials like S3.
There is no way to provide a existingSecret to avoid putting these credentials in the Helm Values.
The text was updated successfully, but these errors were encountered: