You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: