Feature request: OCI registry as backup storage location #9484
Description
Describe the problem/challenge you have
Currently, Velero requires an S3-compatible object storage (AWS S3, MinIO, GCS, Azure Blob, etc.) to store backups. This means users need to maintain separate infrastructure for:
- Container registry (for application images)
- Object storage (for Velero backups)
This adds operational complexity, especially in air-gapped environments or smaller deployments where minimizing infrastructure components is important.
Describe the solution you'd like
Add support for OCI-compliant container registries as a backup storage location. Backups could be stored as OCI artifacts using libraries like ORAS.
This would allow users to leverage their existing container registry infrastructure (Harbor, Docker Registry, GitHub Container Registry, etc.) for storing Velero backups, eliminating the need for a separate object storage system.
Anything else you would like to add:
Has the team considered this approach before? I'd be interested to hear any thoughts on feasibility or potential challenges.
Related projects that store artifacts in OCI registries:
- Helm (charts as OCI artifacts)
- Flux (OCI artifacts support)
- ORAS (generic OCI artifact tooling)
Environment:
N/A (feature request / question)
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"