Note: goal is to change things in one place and have it used by both carvel tooling and also Helm.
Currently, we update Go code, helm, and then carvel.
Maybe have a sed script.
Notes on k8s pull policy
Do we want to have a flag to set the k8s pull policy? Maybe not bc it's just an issue for developers? See what Carvel does. It'd be preferable to do it with Carvel than to modify the [[Velero]] install to add that. Carvel probably has a better way to handle how to configure the whole cluster.
This is relevant to get around the issue of "latest" caching when the pull policy is not set to "always". This pertains to caching Velero and plugin images.
Create a design doc for Carvel YTT
Epic: #3493 design work
Knowledge base
Project: Carvel - Home
Good resources:
Secondary:
Goal
Note: goal is to change things in one place and have it used by both carvel tooling and also Helm.
Notes on k8s pull policy
Do we want to have a flag to set the k8s pull policy? Maybe not bc it's just an issue for developers? See what Carvel does. It'd be preferable to do it with Carvel than to modify the [[Velero]] install to add that. Carvel probably has a better way to handle how to configure the whole cluster.