You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this I can make sure my pvc stays alive when I uninstall a chart.
Is your feature request related to a problem? Please describe.
I once lost important data after uninstalling a chart.
Describe the solution you'd like
I want to be able to add the annotation helm.sh/resource-policy: keep
on a pvc.
Describe alternatives you've considered
I thought of making separate charts for pvcs, but still, they can be uninstalled.
Additional context
I got the information that you had issues with stale and obsolete pvcs.
The idea with this annotation is to set it, where really important data is stored, and persistence shall survive the chart.
Such a pvc needs manual deletion with a kube-ctl command.
The text was updated successfully, but these errors were encountered:
ytsurk
changed the title
[{chart-name}] adding annotations to persistant volume claims
[common] Allowing annotations on persistent volume claims
Oct 8, 2024
In my kubernetes yaml I want to be able to add helm resource polices on pvcs, see
https://helm.sh/docs/howto/charts_tips_and_tricks/#tell-helm-not-to-uninstall-a-resource
With this I can make sure my pvc stays alive when I uninstall a chart.
Is your feature request related to a problem? Please describe.
I once lost important data after uninstalling a chart.
Describe the solution you'd like
I want to be able to add the annotation
helm.sh/resource-policy: keep
on a pvc.
Describe alternatives you've considered
I thought of making separate charts for pvcs, but still, they can be uninstalled.
Additional context
I got the information that you had issues with stale and obsolete pvcs.
The idea with this annotation is to set it, where really important data is stored, and persistence shall survive the chart.
Such a pvc needs manual deletion with a kube-ctl command.
The text was updated successfully, but these errors were encountered: