External-storage: [aws efs] ProvisioningFailed - no volume plugin matched

Created on 24 Jan 2019 · 12Comments · Source: kubernetes-retired/external-storage

I followed the deployment steps and deployed efs-provisioner on kubernetes. But I am getting below error,

$ kubectl describe pvc efs -n dev
Name:       efs
Namespace:  dev
StorageClass:   aws-efs
Status:     Pending
Volume:     
Labels:     <none>
Annotations:    volume.beta.kubernetes.io/storage-class=aws-efs
Capacity:   
Access Modes:   
Events:
  FirstSeen LastSeen    Count   From                SubObjectPath   Type        Reason          Message
  --------- --------    -----   ----                -------------   --------    ------          -------
  8m        23s     11  persistentvolume-controller         Warning     ProvisioningFailed  no volume plugin matched

areawefs lifecyclrotten

Source

harik8

Most helpful comment

nvm, I see it above. The issue is that provisioner is "kubernetes.io/aws-efs". It can't begin with kubernetes.io as that is reserved by kubernetes

wongma7 on 4 Mar 2019

👍3

All 12 comments

I'm having the same issue on EKS, and don't know how to debug it. There are no any erros in efs-provisioner pod logs, EFS is mounted by efs-provisioner, but pvcs are pending with that no volume plugin matched message.

Art3mK on 8 Feb 2019

Looks like it's smth with latest versions. Works fine with chart version 0.1.3 (which uses 0.1.2 image) In order to provision PVC with 0.2.0 chart and v2.1.0-k8s1.11 image you'll need to add volume.beta.kubernetes.io/storage-provisioner: %your provisionerName% annotation to your PVC.

provisioner name could be checked in storage class:

➜  ~ kubectl get storageclasses.storage.k8s.io efs -o yaml --export                                                     
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  creationTimestamp: null
  labels:
    app: efs-provisioner
    chart: efs-provisioner-0.1.3
    env: dev
    heritage: Tiller
    release: efs-provisioner
  name: efs
  selfLink: /apis/storage.k8s.io/v1/storageclasses/efs
parameters:
  gidAllocate: "true"
  gidMax: "50000"
  gidMin: "40000"
provisioner: kubernetes.io/aws-efs
reclaimPolicy: Delete
volumeBindingMode: Immediate

Art3mK on 8 Feb 2019

what version of kubernetes?

/area aws/efs

wongma7 on 4 Mar 2019

We are using EKS one

Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.5-eks-6bad6d", GitCommit:"6bad6d9c768dc0864dab48a11653aa53b5a47043", GitTreeState:"clean", BuildDate:"2018-12-06T23:13:14Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Art3mK on 4 Mar 2019

what does the StorageClass aws-efs look like?

wongma7 on 4 Mar 2019

nvm, I see it above. The issue is that provisioner is "kubernetes.io/aws-efs". It can't begin with kubernetes.io as that is reserved by kubernetes

wongma7 on 4 Mar 2019

👍3

nvm, I see it above. The issue is that provisioner is "kubernetes.io/aws-efs". It can't begin with kubernetes.io as that is reserved by kubernetes

I have the same issue and using kubernetes.io/aws-efs, what should I use then? Thanks.

pulpbill on 1 Apr 2019

IIUC you just need to change provisioner name, as kubernetes.io is reserved. i.e. if you are using efs-provisioner helm chart – set efsProvisioner.provisionerName to some other value.

Art3mK on 1 Apr 2019

👍2 👎1

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 30 Jun 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 30 Jul 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 29 Aug 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.