The following one-time configuration is required to set up the Supervisor cluster:
Steps
Enable the vSphere operator in the Supervisor cluster, for example, the Velero vSphere Operator:
In the left pane of the
vSphere Client, select the workload cluster, and then click the
Configure tab in the right pane.
In the
Workload-Cluster window, scroll down and select
Supervisor Services.
The right pane displays the available services.
Select the
Velero vSphere Operator service, and then click
Enable.
Once enabled, the new Kubernetes namespace gets created automatically with its own vSphere pods running with Supervisor affinity. This allows the Supervisor cluster to perform backups using the FCD snapshot.
Select
Menu > Workload Management to view the namespaces running in the Supervisor cluster. For a selected namespace, click the
Compute tab in the right pane to display the Tanzu guest clusters.
Add a Supervisor namespace for the Velero instance:
In the
Workload Management window of the
vSphere Client, click
New Namespace.
After creating this namespace, select the namespace in the left navigation pane.
If the user does not have the
VI admin role, click
Add Permissions under the
Summary tab in the right pane
In the
Add Permissions dialog, add the
Can edit permission, and then click
OK.
Using the same command line, enable changed block tracking (CBT) in the guest clusters:
# velero-vsphere configure --enable-cbt-in-guests
Once enabled, this setting is applied to the current cluster and all incoming guest clusters.
NOTE In Tanzu Kubernetes clusters with vSphere version 7.0 U2 and later, the command to enable CBT might return the error
Failed to configure CBT on all VMs in guest clusters. If this occurs, verify that you have the cluster admin role or cluster admin privileges, and then perform the following steps:
Manually add the line
`system.serviceaccount.service-account-name.default: "true"` to the ConfigMap under
vmware-system-tkg-system-service-accounts: `kubectl get cm -n vmware-system-tkg vmware-system-tkg-system-service-accounts`, where the
service-account-name matches the name of the namespace created after the Velero operator installation. To obtain this name, you can log into the
vSphere Client, or use the command
kubectl get ns | grep 'svc-velero-vsphere.
Restart the TKGS controller by running the command
kubectl rollout restart deployment vmware-system-tkg-controller-manager -n vmware-system-tkg.
Retry the command
velero-vsphere configure --enable-cbt-in-guests.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\