You’ve one database stateful set, and an unexpected user activity created lot of data, and you’re about to fill the storage. Obviously, you have to increase the storage. But unfortunately, kubernetes doesn’t allow you to increase the storage size in STS(stateful set)


  1. We’ve to check the storageClass which we used allow volume expansion. Means, dynamically expand the storage.
export PVC=<pvc-name>
export STS=<stateful-set-name>
export NS=<namespace>
# Get your storage class name
SC=`kg pvc $PVC -n $NS -o jsonpath='{.spec.storageClassName}'`

# if VolumeExpansion is supported, you'll get the value as true
kubectl get -n $NS -o jsonpath='{.allowVolumeExpansion}' sc $SC

# If the above command gave false, enable volume expansion.
kubectl patch -p '{"allowVolumeExpansion": true}' sc $SC
  1. Increase the storage size of pvc
# First scale the sts to 0
kubectl scale statefulset -n $NS $STS --replicas=0

# Second increase the pvc size ( if you have multiple pvcs, like postgres-0 postgres-1 ..., do it for all of them )

kubectl patch pvc -p '{"spec": {"resources": {"requests": {"storage": "'$NEW_SIZE'"}}}}' -n $NS $PVC

# Note: you won't see the changed volume immediately. So don't worry. Proceed to following steps.
  1. Delete the Statefulset
# Create the backup of current statefulset yaml
kubectl get sts -n $NS $STS -o yaml > sts.yaml

# Edit the statefulset yaml(sts.yaml), and update the `storage: <NEW_SIZE>`
sed -i "s/storage: .*/storage: ${NEW_SIZE}/g" sts.yaml

# Delete the old statefulset
kubectl delete sts -n $NS $STS --cascade=orphan
  1. Recreate the sts
kubectl apply -f sts.yaml
kubectl scale sts -n $NS $STS --replicas=1
  1. Validate the changes
# You should see the updated storage.
kubectl get pvc -n $NS