why do we not need to specify bucket of VolumeSnapshotLocation?

[13567436138]

apiVersion: velero.io/v1
kind: VolumeSnapshotLocation
metadata:
  name: aws-default
  namespace: velero
spec:
  provider: velero.io/aws
  credential:
    key: cred
    name: credentials-velero
  config:
    region: minio
    profile: "default"

[sseago]

Volume snapshots aren't stored in buckets. For the aws provider, volume snapshots are stored in the aws region specified in the VSL. AWS volume snapshots are only relevant for EBS volumes in aws. Minio is only used as an object store, not for native snapshot storage. If you're not using volumes backed by a provider with native snapshot support (aws EBS, gcp, or azure), then you don't need a VolumeSnapshotLocation. For volume backup you'll need to use kopia/restic or the CSI plugin.

[poikilotherm]

Thanks for this perfect answer! It resolved my confusion whether or not I might need to add a VolumeSnapshotLocation when planning on using CSI snaps and data movers (making me not depend on the OpenStack Velero plugin). It would be superb to document this better in the descriptions for CSI as well as the API page for VSL. Do you think a PR would be welcome @sseago ?

[kaovilai]

We welcome all docs improvement PRs. Please submit and we will review.