Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `README.tpl:150-157` </location>
<code_context>
+   RELEASE="besu-network"
+   NAMESPACE="besu"
+
+   for component in validator rpc; do
+     kubectl get pvc -n "${NAMESPACE}" \
+       -l app.kubernetes.io/instance="${RELEASE}",app.kubernetes.io/component="${component}" \
+       -o name \
+     | while read -r pvc; do
+         kubectl patch -n "${NAMESPACE}" "${pvc}" --type merge \
+           -p "{\"spec\":{\"resources\":{\"requests\":{\"storage\":\"${NEW_SIZE}\"}}}}"
+       done
+   done
+   ```
</code_context>

<issue_to_address>
**suggestion:** Consider adding a note about handling failed PVC expansions.

Currently, failed PVC expansions are not reported. Consider implementing error handling or output monitoring to ensure all PVCs are resized as intended.

Suggested implementation:

```
   for component in validator rpc; do
     kubectl get pvc -n "${NAMESPACE}" \
       -l app.kubernetes.io/instance="${RELEASE}",app.kubernetes.io/component="${component}" \
       -o name \
     | while read -r pvc; do
         if kubectl patch -n "${NAMESPACE}" "${pvc}" --type merge \
           -p "{\"spec\":{\"resources\":{\"requests\":{\"storage\":\"${NEW_SIZE}\"}}}}"; then
           echo "Successfully patched ${pvc}"
         else
           echo "ERROR: Failed to patch ${pvc}" >&2
         fi
       done
   done
   ```

```

```
3. Expand the in-use PVCs with plain `kubectl` so the StatefulSets keep running while storage grows:

   > **Note:** The script below will print a message for each PVC indicating success or failure.  
   > If any PVC fails to expand, review the error output and investigate the cause (e.g., insufficient storage, permissions, or cluster limitations).

   ```bash
   NEW_SIZE="200Gi"
   RELEASE="besu-network"
   NAMESPACE="besu"

```
</issue_to_address>

### Comment 2
<location> `README.tpl:161-165` </location>
<code_context>
+4. Confirm every claim reports the larger capacity (wait for `FileSystemResizePending` to clear if your CSI driver performs an in-pod resize):
+
+   ```bash
+   kubectl get pvc -n "${NAMESPACE}" -l app.kubernetes.io/instance="${RELEASE}" -w
+   ```
+
</code_context>

<issue_to_address>
**suggestion:** Consider specifying how long to wait for FileSystemResizePending to clear.

Including expected wait times or guidance for delayed resizing would help operators troubleshoot more effectively.

```suggestion
4. Confirm every claim reports the larger capacity (wait for `FileSystemResizePending` to clear if your CSI driver performs an in-pod resize):

   > **Note:** The `FileSystemResizePending` status typically clears within a few minutes, but may take up to 10–15 minutes depending on your storage backend and cluster load. If the status persists longer than expected, check your CSI driver logs and node status for issues. For troubleshooting, see [Kubernetes PVC resizing documentation](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims).

   ```bash
   kubectl get pvc -n "${NAMESPACE}" -l app.kubernetes.io/instance="${RELEASE}" -w
   ```
```
</issue_to_address>