Helm EKS Fargate + EFS: PVC未绑定，但荚重新启动会有所帮助

Question

在一个舵机图中，我部署了一个PersistentVolume (EFS)：

apiVersion: v1
kind: PersistentVolume
metadata:
  name: {{ .Release.Namespace }}-{{ .Release.Name }}
spec:
  capacity:
    storage: 5Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  storageClassName: {{ .Values.pv.storageClassName }}
  csi:
    driver: efs.csi.aws.com
    volumeHandle: {{ .Values.pv.volumeHandle | quote }}
  claimRef:
    name: {{ .Release.Name }}
    namespace: {{ .Release.Namespace }}

而PersistentVolumeClaim则是：

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: {{ .Release.Name }}
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: {{ .Values.pv.storageClassName }}
  resources:
    requests:
      storage: 5Gi  # Required but ignored in case of EFS
  volumeName: {{ .Release.Namespace }}-{{ .Release.Name }}

一个吊舱像往常一样使用PVC：

volumeMounts:
  - name: persistent-storage
    mountPath: /efs

...
  volumes:
    - name: persistent-storage
      persistentVolumeClaim:
        claimName: {{ .Release.Name }}

当我执行舵机安装时，我有一个浮动问题:豆荚持续处于挂起状态，下一个事件是：

警告FailedScheduling 56s Fargate调度程序Pod在Fargate上不支持:卷不支持:由于: PVC someRelease不绑定而不支持持久存储

如果我要检查PVC的状态，它处于绑定状态，在荚重新启动之后，它就会像预期的那样工作。在PVC试图访问它的时候，PV似乎还没有创建，因此无法创建吊舱。我应该以某种方式指定模板的订单，还是有另一个解决方案？

Answer 1

尝试以下几点：

apiVersion: v1
kind: PersistentVolume
metadata:
  name: {{ .Release.Name }}
spec:
  capacity:
    storage: 5Gi
  volumeMode: Filesystem
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Retain
  storageClassName: ""
  csi:
    driver: efs.csi.aws.com
    volumeHandle: {{ .Values.pv.volumeHandle | quote }}
  claimRef:
    name: {{ .Release.Namespace }}-{{ .Release.Name }}


apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: {{ .Release.Namespace }}-{{ .Release.Name }}
  namespace: {{ .Release.Namespace }}
spec:
  accessModes:
    - ReadWriteMany
  storageClassName: ""
  resources:
    requests:
      storage: 5Gi  # Required but ignored in case of EFS