The Tanzu Kubernetes clusters are hosted by vCenter server; therefore, the vCenter server gets registered with PowerProtect Data Manager. PowerProtect Data Manager discovers the namespaces as assets.
FQDN of vCenter server
vCenter server is successfully registered with PowerProtect Data Manager and is available under Infrastructure > Asset Sources.
The associated supervisor clusters and control plane VMs with the vCenter are available as assets and are available under Infrastructure > Assets > Virtual Machine.
The Tanzu Kubernetes cluster is added successfully, and the namespaces are available under Assets > Kubernetes.
Note: The vCenter hosting Tanzu Cluster is registered with PowerProtect Data Manager and the namespaces are available to be protected. At the time of integration between PowerProtect Data Manager and Tanzu Kubernetes cluster, velero-ppdm and powerprotect, the two namespaces are created on Tanzu Kubernetes cluster.
The powerprotect namespace contains powerprotect-controller pod, and velero-ppdm namespace contains velero pod and backup-driver pod. The backup-driver pod is responsible for taking and deleting snapshots for paravirtualized CSI volumes of Tanzu Kubernetes clusters.