search

vmware-tanzu / velero

Backup and migrate Kubernetes applications and their persistent volumes
https://velero.io
Apache License 2.0
8.53k stars 1.38k forks source link

Minio support on-premise #5049

Open igorkatz opened 2 years ago

igorkatz commented 2 years ago

Hi, I’m using the latest helm chart and the latest client:

velero version
Client:
    Version: v1.9.0
    Git commit: 6021f148c4d7721285e815a3e1af761262bff029
Server:
    Version: v1.9.0

I’m using velero/velero-plugin-for-csi:v0.3.0 CSI plugin I’m using Kubernetes v1.22.5 on-premise and trying perform backup to Minio Backup completed successfully, but VolumeSnapshots are left in the source namespace of the workload after a backup finish. Looks like that Velero doesn't support moving snapshots into the S3 object storage. Should it work in this version? If not, when do you plan to support this? How would you recommend working now?

qiuming-best commented 2 years ago

@igorkatz the CSI snapshot should be supported by the backend provider's CSI driver. So if you are using the on-premise way, it wouldn't work by CSI plugin

qiuming-best commented 2 years ago

@igorkatz you can choose to use restic to do the file system level bakcup

igorkatz commented 2 years ago

My storage provisioner supports volume snapshots and they are created invoked by Velero, but Velero is not moving them into MinIO S3 object storage and the snapshots remain in the source namespace of the workload after a backup finish. Should it work in this Velero version? If not, when do you plan to support this?

sseago commented 2 years ago

@igorkatz That's the data mover use case we're working on in the 1.10 time frame. As it is now, the CSI plugin works best with provisioners which already store volume snapshot contents off-cluster. For provisioners which don't do this, you'll need the data mover for true off-cluster backups.

euclidsun commented 2 years ago

Please notes this "Since v0.3.0 the velero team will provide official support for CSI plugin when they are used with AWS and Azure drivers." and what was validated: https://github.com/vmware-tanzu/velero-plugin-for-csi

reasonerjt commented 1 year ago

Per discussion in v1.11 we will have a more detailed design to cover the data movement use case, therefore this issue will be fixed in release after v1.11