Can this driver create persistent volumes automatically, when a persistent volume claim request is created ?

[ghost]

This scenario is use full in case of stateful set deployments where VolumeClaimTempletes are created
if this possible , please let me know how to implement it
Thank You

[msau42]

createvolume support was recently added in #53. It creates subdirectories from an existing nfs server. Does that address your use case?

[ghost]

I am using CFCR cluster with AWS as IaaS and EFS as persistent volume storage
earlier i was using efs-provisioner to manage storage request.
What I want is when ever a persistent volume claim request is made by user , efs driver should automatically create persistent volume object for it without any manual intervention
Is that possible?
As of now we have to create a PV after deploying driver and in pv object we specify efs id :

apiVersion: v1
kind: PersistentVolume
metadata:
name: data-nfsplugin
labels:
name: data-nfsplugin
spec:
accessModes:

• ReadWriteMany
  storageClassName: efs-sc
  mountOptions:
  • nfsvers=4.1
    capacity:
    storage: 100Gi
    csi:
    driver: nfs.csi.k8s.io
    volumeHandle: fs-xxx
    volumeAttributes:
    server: fs-xxxx.efs.us-east-1.amazonaws.com
    share: /

---

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: data-nfsplugin
spec:
accessModes:

• ReadWriteMany
  storageClassName: efs-sc
  selector:
  matchLabels:
  name: "data-nfsplugin"
  resources:
  requests:
  storage: 100Gi

*** this is the sample file we need to create now , where we provide efs is and server name in persistent volume object and then create claim object
I want to provide efs details in efs driver it self so that persistent volume objects are created dynamically whenever claim request is made

[msau42]

For efs, my understanding is it requires a special mount.efs, which won't work with this driver which is mainly for general nfs servers. I would suggest asking in https://github.com/kubernetes-sigs/aws-efs-csi-driver

[ghost]

hey @msau42 than you for your response. In our case we are using CFCR cluster and as far as I know aws-efs-csi driver is specific to aws eks cluster

[msau42]

The efs driver can be used in any aws based Kubernetes ctuster

[ghost]

Hi @msau42 , I downloaded the latest version of this repo with create volume changes and tried to deploy but controller pods are going into crashloop backoff state with following logs on csi-provisioner and liveliness container
1 connection.go:170] Still connecting to unix:///csi/csi.sock

[msau42]

does the nfsplugin have any error messages? Are you using canary image?

[ghost]

Hi @msau42 above issue is resolved by changes mount paths. but how will this create persistent volume on persistent volume claim request. In you example file of storage class i have specified my aws efs server by pv is not not getting created and pod is going into pending state with error
pod has unbound immediate PersistentVolumeClaims

storage class fie looks like this

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: nfs-csi
provisioner: nfs.csi.k8s.io
parameters:
server: fs-xxxx.efs.us-east-1.amazonaws.com
share: /
accessModes: ReadWriteOnce
reclaimPolicy: Retain # only retain is supported
volumeBindingMode: Immediate
mountOptions:

• hard
• nfsvers=4.1

I want to store my data on EFS and not on local storage , so where should I specify my efs id
and can you please give a detailed read me file on what steps to be followed , what is use of controller fie if provisioning is done by nfs-server.yaml

[andyzhangx]

Hi @msau42 above issue is resolved by changes mount paths. but how will this create persistent volume on persistent volume claim request. In you example file of storage class i have specified my aws efs server by pv is not not getting created and pod is going into pending state with error
pod has unbound immediate PersistentVolumeClaims

storage class fie looks like this

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: nfs-csi
provisioner: nfs.csi.k8s.io
parameters:
server: fs-xxxx.efs.us-east-1.amazonaws.com
share: /
accessModes: ReadWriteOnce
reclaimPolicy: Retain # only retain is supported
volumeBindingMode: Immediate
mountOptions:

• hard
• nfsvers=4.1

I want to store my data on EFS and not on local storage , so where should I specify my efs id
and can you please give a detailed read me file on what steps to be followed , what is use of controller fie if provisioning is done by nfs-server.yaml

@lordcf could you make sure your nfs server config is correct? You could manually check by mount -v -t nfs -o ... nfs-server:/path mount-path and if there is error in driver side, check by https://github.com/kubernetes-csi/csi-driver-nfs/blob/master/docs/csi-debug.md#csi-driver-debug-tips

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

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-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

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-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@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-contributor-experience at kubernetes/community.
/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.