A user asked:
Is there a recommended way to not delete certain helm resources on a tilt down, such as a storageclass?
StorageClass is a cluster-wide resource for configuring a type of storage.
To me, it's similar to a namespace, which we had a similar discussion about:
#3160
#2805
Should we treat StorageClasses the same way, and only delete them if you pass a special flag?
I really admire the Helm solution to this:
https://helm.sh/docs/topics/charts_hooks/
where you can add annotations to a resource like:
"helm.sh/hook": post-install
"helm.sh/hook-weight": "-5"
"helm.sh/hook-delete-policy": hook-succeeded
to specify what helm should do with a resource at different stages of the lifecycle. So you could imagine a Tilt annotation like:
"tilt.dev/down-policy": keep
A user asked:
StorageClass is a cluster-wide resource for configuring a type of storage.
To me, it's similar to a namespace, which we had a similar discussion about:
#3160
#2805
Should we treat StorageClasses the same way, and only delete them if you pass a special flag?
I really admire the Helm solution to this:
https://helm.sh/docs/topics/charts_hooks/
where you can add annotations to a resource like:
to specify what helm should do with a resource at different stages of the lifecycle. So you could imagine a Tilt annotation like: