You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if this is a kops issue but definitely seeing this problem on K8S cluster installed using KOPS. I created a physical volume that uses NFS (AWS EFS) but PVC is not binding to it. Instead it creates another EBS disk. Here is the log:
> kubectl get pv
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
mynfspv 100Gi RWX Retain Available 7s
create PVC now
> kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESSMODES STORAGECLASS AGE
mynfspvc Bound pvc-a081c470-3f23-11e7-9d30-024e42ef6b60 100Gi RWX default 4s
> kubectl get pv
NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM STORAGECLASS REASON AGE
mynfspv 100Gi RWX Retain Available 50s
pvc-a081c470-3f23-11e7-9d30-024e42ef6b60 100Gi RWX Delete Bound default/mynfspvc default 17s
Thanks. I also figured that I can add a tag "storageClassName" on both PV and PVC to make this work. For example, I added "storageClassName: slow" on both PV and PVC.
I am not sure if this is a kops issue but definitely seeing this problem on K8S cluster installed using KOPS. I created a physical volume that uses NFS (AWS EFS) but PVC is not binding to it. Instead it creates another EBS disk. Here is the log:
create PVC now
nfs-pv.yaml
nfs-pvc.yaml
The text was updated successfully, but these errors were encountered: