An administrator has been tasked with enabling backup for a vSphere Kubernetes cluster.

In VCF 9.0 Workload Management, workload backup for VKS clusters (and vSphere Pods) is performed using Velero, specifically theVelero Plugin for vSpherefor Supervisor/VKS scenarios. The documentation describes that you must firstprovide an S3-compatible object storeas part of installing and configuring the Velero Plugin for vSphere, because backup data (Kubernetes metadata and volume snapshot data movement) relies on object storage rather than “namespace storage.” The backup workflow further indicates that when you create a backup, the system uploadsKubernetes metadata to the object store, and persistent volume snapshot handling is coordinated through the plugin components (Snapshot/Upload custom resources).

Therefore, the correct configuration pattern is to point Velero’s backup target (BackupStorageLocation) at anS3-compatible object storeendpoint so metadata and snapshot payloads have a durable destination. This aligns with the documented prerequisite that object storage is required to enable backup/restore operations for persistent workloads, and it is the mechanism Velero uses to store backup artifacts for later restore operations in VKS environments.