Open jaimegag opened 3 years ago
Let's build a single doc to cover Velero that all RAs can refer to.
Do consult with Chad Moon on testing & docs he previously did with TKG + Velero.
TKO is focused on advocating Tanzu SaaS, that is why we have included data protection through TMC which eventually installs velero in the workload clusters.
Installing Velero standalone is only recommended in airgap environments or where TMC data protection cannot provide the required feature.
For 2.0 doc, we have created a dedicated md for Data Protection RA and Deploy Guide and all the existing RA/DG are pointing to cross-linked/referenced to data protection doc.
I will reach out to Velero PM to check on supportability when velero installation is manual
Hi @manishjha86 , a couple of things
1) When this issue was opened the RA instruction about Velero were manual steps with Velero OSS CLI and not TMC driven. This issue was a recommendation to use the Velero CLI bits we distribute with TKGm instead the OSS Velero CLI bits. Of course on TKO, we should advocate for the TMC data protection first. But for anybody doing Velero standalone, they should stick to the Commercial bits we distribute instead of the OSS ones.
2) I can confirm that Velero standalone is fully supported as part of the Tanzu Basic/Standard/Advanced, and so TKO too. So anybody with a TKGm entitlement can get support when using Velero directly and not only via TMC. We distribute signed Velero bits alongside the TKGm bits https://customerconnect.vmware.com/en/downloads/details?downloadGroup=TKG-154&productId=988&rPId=88961, and this is documented in the TKGm official docs: https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid/1.5/vmware-tanzu-kubernetes-grid-15/GUID-cluster-lifecycle-backup-restore-mgmt-cluster.html
Manual documentation of Velero on TKGm apart from TMC will be validated and updated in the upcoming RA
Velero instructions should point to the TKGm downloads section in my.vmware.com (scroll to bottom) instead of describing how to install the OSS bits via Golang; and the deployment examples should explicitly use the built and signed images from our repo.