Skip to content
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

Provide existing secret for restic backups #191

Open
ldaneliukas opened this issue Nov 17, 2023 · 1 comment
Open

Provide existing secret for restic backups #191

ldaneliukas opened this issue Nov 17, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@ldaneliukas
Copy link
Collaborator

ldaneliukas commented Nov 17, 2023

Use Case

In order to use restic for backups, you need to commit plain-text secrets into your VCS since the chart does not allow using an existing secret for these credentials.

Describe the Solution You Would Like

Use of existing secret for restic S3 credentials, similarly to the way that PostgreSQL secrets are already handled.

Describe Alternatives You've Considered

  • Using plain text secrets, but that's not really an alternative.
  • Injecting require Helm values from CI/CD (e.g. from GitHub Actions secrets) which works, but it'd be nicer to be able to use a pre-existing secret as it can be pre-created by Vault (or similar) in most Kubernetes setups.

Additional Context

I can create a PR for this.

@ldaneliukas ldaneliukas added the enhancement New feature or request label Nov 17, 2023
@Xtigyro
Copy link
Contributor

Xtigyro commented Nov 27, 2023

Same here - please create a PR if you can.
CC: @davidphay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants