https://pulumi.com logo
#kubernetes
Title
# kubernetes
s

steep-angle-29984

12/14/2020, 5:59 PM
I was wondering how you guys deal with persistent storage (e.g. StorageClasses, PersistentVolumeClaims, PersistentVolumes) using pulumi. Because of the way pulumi generates the names by adding random strings as postfix, I fear data loss when resources are replaced. Some Helm-Charts (e.g. Elastic Cloud on Kubernetes, Kube-Prometheus-Stack) offer the option of specifying a volumeClaimTemplate. I consider to create a StorageClass and a PV with a fixed name (no auto-naming) before installing these Helm-Charts and then bind them via the volumeClaimTemplate. That way I can define the reclaim policy as 'Retain' and replaced resources will hopefully always be bound to the same PV. Is that a good idea?
3 Views