From 222a54a9035e7cb31c28d3b507d918469fd2063c Mon Sep 17 00:00:00 2001
From: Pierre Besson <pierre.besson@parity.io>
Date: Mon, 13 Jun 2022 14:36:42 +0100
Subject: [PATCH] add docs on how to resize node persistent volumes

---
 charts/node/README.md | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/charts/node/README.md b/charts/node/README.md
index 8c7f9b4f..51eff278 100644
--- a/charts/node/README.md
+++ b/charts/node/README.md
@@ -22,6 +22,27 @@ helm install kusama-node parity/node --set node.chainDataSnapshotUrl=https://ksm
 ```
 ⚠️ For some chains where the local directory name is different from the chain ID, `node.chainPath` needs to be set to a custom value.
 
+### Resizing the node disk
+
+To resize the node persistent volume, perform the following steps:
+
+1. Patch the PVC storage size, eg. to `1000Gi`:
+
+```console
+kubectl patch pvc chain-data-polkadot-node-0  -p '{"spec":{"resources":{"requests":{"storage":"1000Gi"}}}}}'
+```
+
+2. Delete the StatefulSet object with `cascade=orphan` (ie. without removing the attached pods):
+
+```console
+kubectl delete sts polkadot-node --cascade=orphan
+```
+
+3. Update the `node.dataVolumeSize` to the new value (eg. `1000Gi`) and upgrade the helm release.
+
+Note that for a Kubernetes Persistent Volume Claims to be resizable, its StorageClass must have specific characteristics. More information on this topic is available in the [Expanding Persistent Volumes Claims
+section of the Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims).
+
 ### Optional Vault Integration
 
 To integrate this chart with vault: