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

Allow Velero to support multiple credentials per storage provider #3304

Closed
nrb opened this issue Jan 19, 2021 · 2 comments
Closed

Allow Velero to support multiple credentials per storage provider #3304

nrb opened this issue Jan 19, 2021 · 2 comments
Assignees
Labels
Enhancement/User End-User Enhancement to Velero
Milestone

Comments

@nrb
Copy link
Contributor

nrb commented Jan 19, 2021

Describe the problem/challenge you have
Currently, Velero can only have 1 credential for a given storage platform, which is limiting if backups should be sent to different locations. For example, if someone is using GCP and wants to send backups to 2 different object storage buckets, this is not currently supported.

Describe the solution you'd like
Velero should offer some way to allow all storage provider platforms the ability to utilize multiple credential files. This should work for object storage only. Handling of volume snapshots will not be changed and they will continue to use the existing credentials provided during install.

Anything else you would like to add:
AWS can get around this by specifying profiles in the credential file, but not all file formats offer this support.

Also, restic support should be taken into account as it is currently part of Velero's core, not a plugin.

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

  • 👍 for "The project would be better with this feature added"
  • 👎 for "This feature will not enhance the project in a meaningful way"
@zubron
Copy link
Contributor

zubron commented Mar 12, 2021

Fixed in #3442, #3489, and #3559.

@zubron zubron closed this as completed Mar 12, 2021
@zubron
Copy link
Contributor

zubron commented Mar 12, 2021

Note: updated issue description to remove reference to volume snapshots as this will only affect object storage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement/User End-User Enhancement to Velero
Projects
None yet
Development

No branches or pull requests

2 participants