Restore Specific Namespaces.

Note:

  • If TCA add-on load-balancer-and-ingress-service is enabled in the source cluster and a CNF is defined to create Kubernetes resources gatewayclasses.networking.x-k8s.io or gateways.networking.x-k8s.io in the Helm Chart, CNF pods in the restore namespaces will be in "Pending" state after restoration is complete. Recreate the resources in the restored cluster with new service engine group setting. It is recommended to define these resources in the TCA add-on instead.

  • If TCA cert-manager add-on is enabled in the cluster and CNF is configured to use this add-on, cert-manager service won't be able to renew certificates requested by this CNF any more after the namespace where the CNF is restored. In such case, reconfigure the CNF from TCA to generate missing resources after the restore process.

Prerequisites

Install and Configure Velero Add-On for the Workload Clusters.

Procedure

  1. Log in to the VMware Telco Cloud Automation web interface.
  2. Navigate to Infrastructure > Virtual Infrastructure.
  3. Open the web terminal by clicking the Options (three dots) corresponding to the workload cluster you want to backup and then selecting Open Terminal.
  4. On the Web terminal, check the service health of Velero by running the following command: 
    # kubectl get pod -n velero 
# kubectl get bsl -n velero
  5. Get backup information. 
    # velero backup get
  6. Delete the namespaces that will be restored from a backup. 
    # kubectl delete namespaces <example-namespaces-by-comma>
  7. Restore specific namespaces to the cluster. 
    # velero restore create --from-backup <example-backup>
  8. Check backup status and uploads CR and wait until they are both "Completed". 
    # velero restore get // check the restore status
# kubectl get downloads -n velero // get the download-name 
# kubectl get downloads <download-name> -o yaml // check the downloads status in yaml output