dynamic-nfs-provisioner

dynamic-nfs-provisioner copied to clipboard

For Mac M1, I am trying to dynamically provision a PV for my minikube cluster. I am following this docs https://github.com/openebs/dynamic-nfs-provisioner/blob/develop/docs/intro.md I have storage class, pvc in my cluster. But, pv is not dynamically getting provisioned. Did anyone saw this behaviour before?

➜  ebs-nfs-provisioner k get sc | grep openebs-rwx
openebs-rwx          openebs.io/nfsrwx                                 Delete          Immediate              false                  13m

➜  ebs-nfs-provisioner k get pvc
NAME      STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
nfs-pvc   Pending                                      openebs-rwx    10m

➜  ebs-nfs-provisioner k describe sc openebs-rwx
Name:            openebs-rwx
IsDefaultClass:  No
Annotations:     cas.openebs.io/config=- name: NFSServerType
  value: "kernel"
- name: BackendStorageClass
  value: "openebs-hostpath"
#  LeaseTime defines the renewal period(in seconds) for client state
#- name: LeaseTime
#  value: 30
#  GraceTime defines the recovery period(in seconds) to reclaim locks
#- name: GraceTime
#  value: 30
#  FSGID defines the group permissions of NFS Volume. If it is set
#  then non-root applications should add FSGID value under pod
#  Supplemental groups
#- name: FSGID
#  value: "120"
,kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"storage.k8s.io/v1","kind":"StorageClass","metadata":{"annotations":{"cas.openebs.io/config":"- name: NFSServerType\n  value: \"kernel\"\n- name: BackendStorageClass\n  value: \"openebs-hostpath\"\n#  LeaseTime defines the renewal period(in seconds) for client state\n#- name: LeaseTime\n#  value: 30\n#  GraceTime defines the recovery period(in seconds) to reclaim locks\n#- name: GraceTime\n#  value: 30\n#  FSGID defines the group permissions of NFS Volume. If it is set\n#  then non-root applications should add FSGID value under pod\n#  Supplemental groups\n#- name: FSGID\n#  value: \"120\"\n","openebs.io/cas-type":"nfsrwx"},"name":"openebs-rwx"},"provisioner":"openebs.io/nfsrwx","reclaimPolicy":"Delete"}
,openebs.io/cas-type=nfsrwx
Provisioner:           openebs.io/nfsrwx
Parameters:            <none>
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>

➜  ebs-nfs-provisioner k describe pvc nfs-pvc
Name:          nfs-pvc
Namespace:     default
StorageClass:  openebs-rwx
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: openebs.io/nfsrwx
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       <none>
Events:
  Type    Reason                Age                 From                         Message
  ----    ------                ----                ----                         -------
  Normal  ExternalProvisioning  45s (x42 over 10m)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "openebs.io/nfsrwx" or manually created by system administrator

I am seeing the same behavior with minikube v1.30.1 on Darwin 13.3.1. I do not run on a M1 processor. Is minikube supported?

Hi, We can also see the same behavior for MicroK8s v1.27. Previous versions work fine though.

Hi, I'm facing the same issue: ubuntu 22.04/x86, Microk8s 1.27.1 Not able to provision new volumes, even with standard hostpath after the upgrade.

Hello,

We are currently facing this issue on rocky linux 8.8 as well.