Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Velero page review #30

Open
jaimegag opened this issue Oct 14, 2021 · 6 comments
Open

Velero page review #30

jaimegag opened this issue Oct 14, 2021 · 6 comments
Assignees
Labels
documentation Improvements or additions to documentation wip
Milestone

Comments

@jaimegag
Copy link

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.

@ghost ghost assigned sendjainabhi Jan 7, 2022
@srivar
Copy link

srivar commented Jan 7, 2022

Let's build a single doc to cover Velero that all RAs can refer to.

@ghost ghost assigned manishjha86 and unassigned sendjainabhi Jan 12, 2022
@srivar
Copy link

srivar commented Jan 12, 2022

Do consult with Chad Moon on testing & docs he previously did with TKG + Velero.

@craigtracey craigtracey transferred this issue from another repository Jan 18, 2022
@srivar srivar assigned nithink-vmw and unassigned manishjha86 Mar 2, 2022
@srivar srivar added this to the TKO Reference Architectures 1.5 milestone Mar 2, 2022
@manishjha86
Copy link
Contributor

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.

@manishjha86
Copy link
Contributor

I will reach out to Velero PM to check on supportability when velero installation is manual

@manishjha86 manishjha86 added the backlog Won't fix unless/until field/customer requires this label Jun 1, 2022
@jaimegag
Copy link
Author

jaimegag commented Jun 1, 2022

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

@srivar srivar removed the backlog Won't fix unless/until field/customer requires this label Jun 6, 2022
@srivar srivar modified the milestones: TKO RA 1.5, TKO RA 1.6 Jun 6, 2022
@smuthukumar-vmw smuthukumar-vmw added wip documentation Improvements or additions to documentation labels Jul 12, 2023
@smuthukumar-vmw
Copy link
Collaborator

Manual documentation of Velero on TKGm apart from TMC will be validated and updated in the upcoming RA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation wip
Projects
None yet
Development

No branches or pull requests

6 participants