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
We use Helm charts to deploy VM, sometimes we need to increase storage size. For example, this includes cases when:
the VM load always grows instead of being constant
there's a need to change the retention period for the existing cluster
there's a need to add some spare storage for background merges
With Helm we can't just increase PVC template size for vmstorages because of statefulset constraints in k8s. In order to increase our disks, we either add another replica pod of vmstorage or manually edit resizable PVC in GKE, which is very inconvenient for many reasons.
Some database operators have solved the issue: as I understood their operator patches PVC, then deletes the statefulset with --cascade=false so that pods remain untouched, and then creates the statefulset with renewed storage requests so that new replicas get created with new storage size.
P.S. Further improvements could be, for example, a kind of watcher that automatically adjusts PVCs depending on the "free storage threshold" that a user specifies for VMSingle/VMCluster.
The text was updated successfully, but these errors were encountered:
We use Helm charts to deploy VM, sometimes we need to increase storage size. For example, this includes cases when:
With Helm we can't just increase PVC template size for vmstorages because of statefulset constraints in k8s. In order to increase our disks, we either add another replica pod of vmstorage or manually edit resizable PVC in GKE, which is very inconvenient for many reasons.
Some database operators have solved the issue: as I understood their operator patches PVC, then deletes the statefulset with
--cascade=false
so that pods remain untouched, and then creates the statefulset with renewed storage requests so that new replicas get created with new storage size.A few examples:
elastic/cloud-on-k8s#3752
zalando/postgres-operator#958
P.S. Further improvements could be, for example, a kind of watcher that automatically adjusts PVCs depending on the "free storage threshold" that a user specifies for VMSingle/VMCluster.
The text was updated successfully, but these errors were encountered: