Open cnukwas opened 4 years ago
I have created following PersistentVolume and PersistentVolumeClaim definitions for our Shiny-proxy Kubernetes test environment and noticed that it's mounting to incorrect path instead of given NFS server path.
Any ideas on how to debug this issue?
apiVersion: v1 kind: PersistentVolume metadata: name: nfs-pv labels: name: nfs-pv spec: persistentVolumeReclaimPolicy: Retain storageClassName: manual capacity: storage: 500Mi accessModes:
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: nfs-pvc namespace: sproxy spec: storageClassName: manual accessModes:
Then referred to above PVC as below in application.yaml for one of the applications. container-volumes: ["nfs-pvc:/sproxy/data"]
The file system is shown as /dev/mapper/rootvg-homelv, instead of nfs_host.com:/test server and the path.
I have created following PersistentVolume and PersistentVolumeClaim definitions for our Shiny-proxy Kubernetes test environment and noticed that it's mounting to incorrect path instead of given NFS server path.
Any ideas on how to debug this issue?
PV
apiVersion: v1 kind: PersistentVolume metadata: name: nfs-pv labels: name: nfs-pv spec: persistentVolumeReclaimPolicy: Retain storageClassName: manual capacity: storage: 500Mi accessModes:
PVC
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: nfs-pvc namespace: sproxy spec: storageClassName: manual accessModes:
Then referred to above PVC as below in application.yaml for one of the applications. container-volumes: ["nfs-pvc:/sproxy/data"]
The file system is shown as /dev/mapper/rootvg-homelv, instead of nfs_host.com:/test server and the path.