如何在Helm重新部署时自动将Released状态的PV转为Available？

当Helm重新部署组件时，旧PVC被删除后，PV的claimRef仍指向已删除的PVC，导致PV进入Released状态，无法被新PVC绑定。以下是两种自动化解决方案：

方案一：通过Helm钩子自动清理PV的claimRef #

在Helm chart中添加预部署钩子，在创建新资源前自动清除目标PV的claimRef，使其回到Available状态。

1. 在chart的templates目录下创建pv-cleanup-hook.yaml：

apiVersion: batch/v1
kind: Job
metadata:
  name: pv-cleanup-backend
  annotations:
    "helm.sh/hook": pre-install,pre-upgrade
    "helm.sh/hook-weight": "0"
    "helm.sh/hook-delete-policy": hook-succeeded
spec:
  template:
    spec:
      serviceAccountName: pv-cleanup-sa
      restartPolicy: OnFailure
      containers:
      - name: kubectl
        image: bitnami/kubectl:latest
        command:
        - /bin/sh
        - -c
        - |
          kubectl patch pv backend-pv --type json -p '[{"op": "remove", "path": "/spec/claimRef"}]' || true

2. 创建对应权限的ServiceAccount和RBAC规则（在templates目录下新建rbac.yaml）：

apiVersion: v1
kind: ServiceAccount
metadata:
  name: pv-cleanup-sa
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: pv-cleanup-role
rules:
- apiGroups: [""]
  resources: ["persistentvolumes"]
  verbs: ["patch", "get"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: pv-cleanup-binding
subjects:
- kind: ServiceAccount
  name: pv-cleanup-sa
  namespace: {{ .Release.Namespace }}
roleRef:
  kind: ClusterRole
  name: pv-cleanup-role
  apiGroup: rbac.authorization.k8s.io

每次执行helm install或helm upgrade时，钩子会自动清理backend-pv的关联信息，让PV恢复可用状态。

方案二：阻止Helm删除旧PVC #

如果不需要修改PVC配置，直接让Helm在升级时保留旧PVC，避免PV因PVC被删除进入Released状态。

在PVC模板中添加保留注解：

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: backend-pvc
  annotations:
    "helm.sh/resource-policy": "keep"  # 阻止Helm删除该PVC
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 2Gi
  selector:
    matchLabels:
      pv-name: backend-pv  # 绑定到指定静态PV

添加该注解后，Helm升级时不会删除旧PVC，PV会持续与PVC绑定，重部署的Pod可直接挂载。

内容的提问来源于stack exchange，提问作者Jesus Montilla