This section describes how to back up and restore Kubernetes clusters provisioned by Tanzu Kubernetes Grid Integrated Edition.


TKGI uses BOSH Backup and Restore (BBR) to back up and restore Kubernetes clusters provisioned by TKGI. For more information about BBR, see BOSH Backup and Restore.

BBR orchestrates triggering the backup or restore process on the BOSH deployment, and transfers the backup artifacts to and from the BOSH deployment.

In context of Kubernetes clusters provisioned by TKGI, BBR backs up and restores the following components:

  • TKGI cluster control plane nodes
  • TKGI cluster worker nodes

BBR can also be used to backup and restore the TKGI Management Plane. See Backup and Restore TKGI Components.

In context of TKGI, BBR does not back up and restore:

To use BBR to backup and restore Kubernetes clusters provisioned by TKGI, see the following topics:

Testing Considerations

As part of your TKGI backup and restore planning and testing, consider the following test scenario.

  • Take backup of a TKGI-provisioned Kubernetes cluster using BBR.
  • Delete the cluster control plane and worker node VMs. Delete the disks and references.
  • Restore cluster nodes using BBR. Delete old worker nodes using kubectl and restart kubelet.

The cluster nodes should be restored, and the cluster should be operational. If an application was deployed before cluster backup, the VIP of the load balancer for the application changes. To recover without application redeployment, create the service using a static IP. How to do this is described in the workload backup and restore documentation. If an application was deployed after cluster backup, the application is no longer available and the NSX-T objects created for the application are automatically deleted. In this case you will need to restore the application using Velero and the NSX-T objects using NSX Manager.

check-circle-line exclamation-circle-line close-line
Scroll to top icon