feat: make StorageClass reclaimPolicy configurable via values.yaml

[srikxcipher]

Problem

reclaimPolicy: Delete is hardcoded as a literal in deploy/helm/templates/storageclass.yaml for all six cloud providers (AWS, GCP, Alibaba, Tencent, Azure, Huawei). Other
fields in the same template — volumeType, fsType — are already templated through values.yaml, but reclaimPolicy is not.

This means there is no way to set reclaimPolicy: Retain on the KubeBlocks-provisioned StorageClass without either skipping StorageClass creation entirely or patching every
PV individually after provisioning. For datastore workloads (MongoDB, PostgreSQL, MySQL, Redis), this removes the standard Kubernetes safety net against accidental PVC
deletion — particularly dangerous when combined with terminationPolicy: Delete, which explicitly deletes PVCs during cluster teardown.

Changes

• deploy/helm/templates/storageclass.yaml — replaced hardcoded reclaimPolicy: Delete in all six provider blocks with {{ .Values.storageClass.reclaimPolicy | default "Delete" }}
• deploy/helm/values.yaml — added storageClass.reclaimPolicy with default Delete

Behaviour

• Default is Delete — zero change for any existing install unless the value is explicitly set
• To opt in: helm upgrade kubeblocks kubeblocks/kubeblocks --set storageClass.reclaimPolicy=Retain

Migration note for existing clusters

reclaimPolicy is inherited by each PV at creation time only. Changing the StorageClass does not retroactively update already-provisioned PVs. Existing PVs must be
patched individually:

kubectl patch pv <pv-name> -p '{"spec":{"persistentVolumeReclaimPolicy":"Retain"}}'                                                                                          
                                                                                                                                                                             
References                                                                                                                                                                   
                                                                                                                                                                             
- Kubernetes docs on reclaim policy: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#reclaiming                                                              
- Related: terminationPolicy gap for datastore workloads (Halt removal in v1.0)                                                                                              
                                                                                                                                                                             
---

[CLAassistant]

All committers have signed the CLA.

[apecloud-bot]

Auto Cherry-pick Instructions

Usage:
  - /nopick: Not auto cherry-pick when PR merged.
  - /pick: release-x.x [release-x.x]: Auto cherry-pick to the specified branch when PR merged.

Example:
  - /nopick
  - /pick release-1.1

[shanshanying]

hi @srikxcipher don't forget to sign the CLA.

[srikxcipher]

hi @srikxcipher don't forget to sign the CLA.

Done ...

[apecloud-bot]

/cherry-pick release-1.1

[apecloud-bot]

/cherry-pick release-1.0

[apecloud-bot]

🤖 says: cherry pick action finished successfully 🎉!
See: https://github.com/apecloud/kubeblocks/actions/runs/21742027639

[apecloud-bot]

🤖 says: cherry pick action finished successfully 🎉!
See: https://github.com/apecloud/kubeblocks/actions/runs/21742028254