CODEWITHSUNDEEP
kuberneteskubernetes-helmamazon-eksaws-fargateamazon-efs
Anton Balashov
Anton Balashov

Reputation: 1030

Helm EKS Fargate + EFS: PVC not bound, but pod restart helps

Within one helm chart I deploy a 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 }}

And PersistentVolumeClaim for it:

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 }}

And a pod uses the PVC as usual:

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

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

When I do helm install, I have a floating issue: pods continuously in a pending state with the next event:

Warning FailedScheduling 56s fargate-scheduler Pod not supported on Fargate: volumes not supported: persistent-storage not supported because: PVC someRelease not bound

If I would check state of the PVC, it's in Bound state and after a pod restart it works as expected. It looks like PV is not created yet at the moment when PVC tries to access it, hence the pod can't be created. Should I specify an order for the templates somehow or there is another solution?

Upvotes: 0

Views: 1503

Answers (1)

gohm'c
gohm'c

Reputation: 15500

Try the following:

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

Upvotes: 2

Related Questions