Velero creates a different file/folder structure for each cluster it backs up. To restore a backup to a cluster different from the original cluster the backup was created on, you must mount the backup location from the source cluster to the destination cluster. You can use the Velero CLI to add additional backup locations to a cluster.
An airgap install is used when the environment is unable to connect to the public VMware registries during TKG install, cluster creation or upgrades. Internet restricted environments can use an internal private registry in place of the VMware public registry. Most private registries utilize either a self-signed or internal CA signed certificate. Container engines like Contained and Docker do not trust insecure registries by default. The below process covers how install TKG using a private registry configured with a self-signed or internal CA signed certificate.
Failure to correctly configure containerd on the bootstrap/managment cluster(s) will cause the TKG install to fail. In most cases the install will time-out waiting for cert-manager to become available. Troubleshooting on the bootstrap/mgmt cluster will show x509 certificate signed by unknown authority errors in POD logs. The process will also be needed to create an
https://github.com/helm/charts/tree/master/stable/prometheus-operator