Requirements for the Carvel integration

vmware-tanzu / velero

Backup and migrate Kubernetes applications and their persistent volumes

https://velero.io

Apache License 2.0

8.77k stars 1.41k forks source link

Requirements for the Carvel integration #3742

Closed carlisia closed 2 years ago

carlisia commented 3 years ago

Epic: #3493 design work

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

:+1: for "The project would be better with this feature added"
:-1: for "This feature will not enhance the project in a meaningful way"

nrb commented 3 years ago

Configuration data from a distribution like TKG should flow into Velero deployments. For example, if deploying TKG on AWS, the Velero variables in ytt should read from that same information.

Another way to say this is to use generic, distro-level parameters should be re-used for our overlays and packaging.

nrb commented 3 years ago

Make sure that generating a Helm Chart is possible from the same base manifests that Carvel will consume; combining helm and Carvel generation in v1.7.0 is a non-goal

nrb commented 3 years ago

Being about to use the Carvel info as a source of truth for velero install, so that our install command is a wrapper around the toolset.

This will eventually deprecate the go install package.

carlisia commented 2 years ago

Closing this as it has been done in the TCE repo.