Pre-binding PVC to PV through claimRef works fine on creation.
But it seems like editing PV manifest afterwards will break things (especially in case of removing spec.claimRef.uid).
E. g. on my kubernetes provider it unbinds PVC and errors it out due to multiple bindings to same PV.
This becomes an issue if the chart is under some gitops solution (like Argo CD) that will continuously apply manifests from chart re-renders.
Fortunately, everything works fine when using volumeName reference in PVC.
Although this way PV could be bound to something else in case of storageClass collision, it doesn't seem like a big issue to me.
Pre-binding PVC to PV through
claimRefworks fine on creation. But it seems like editing PV manifest afterwards will break things (especially in case of removingspec.claimRef.uid). E. g. on my kubernetes provider it unbinds PVC and errors it out due to multiple bindings to same PV.This becomes an issue if the chart is under some gitops solution (like Argo CD) that will continuously apply manifests from chart re-renders.
Fortunately, everything works fine when using
volumeNamereference in PVC. Although this way PV could be bound to something else in case ofstorageClasscollision, it doesn't seem like a big issue to me.