Skip to main content


You can perform maintenance for Besu on a Kubernetes cluster.


Update a persistent volume claim size

Over time, as the chain grows, so will the amount of space used by the persistent volume claim (PVC). As of Kubernetes v1.11, certain types of Storage Classes allow volume resizing. Production charts for Azure use Azure Files, and on AWS use EBS Block Store which allow for volume expansion.

To update the volume size, you must update the override values file. For example, to increase the size on the transaction nodes volumes, add the following snippet to the txnode values.yml file, with the new size limit (the following example uses 50Gi).

sizeLimit: "50Gi"
pvcSizeLimit: "50Gi"

Once complete, update the node via helm:

helm upgrade tx-1 ./charts/besu-node --namespace besu --values ./values/txnode.yml

Update Besu versions


When updating Besu nodes across a cluster, perform the updates as a rolling update and not all at once, especially for the validator pool. If all the validators are taken offline, the chain halts, and you must wait for round changes to expire before blocks are created again.

Updates for Besu can be done via Helm in exactly the same manner as other applications. Alternatively, this can be done via kubectl. This example updates a node called besu-validator-3:

  1. Set the update policy to use rolling updates (if not done already):

    kubectl patch statefulset besu-validator-3 --namespace besu -p '{"spec":{"updateStrategy":{"type":"RollingUpdate"}}}'
  2. Update the Besu version via Helm:

    helm upgrade bootnode-1 ./charts/besu-node --namespace besu --values ./values/bootnode.yml --set image.besu.tag=21.10.0

    Or via kubectl:

    kubectl patch statefulset besu-validator-3 --namespace besu --type='json' -p='[{"op": "replace", "path": "/spec/template/spec/containers/0/image", "value":"hyperledger/besu:21.10.0"}]'