<p>I am trying to use <code>NFS</code> volume in the same cluster I have deployed other k8s services. But one of the services using the <code>NFS</code> fails with 
<code>Output: mount.nfs: mounting nfs.default.svc.cluster.local:/opt/shared-shibboleth-idp failed, reason given by server: No such file or directory</code></p>

<p>The <code>nfs PV</code></p>

<pre><code>apiVersion: v1
kind: PersistentVolume
metadata:
  name: nfs
spec:
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteMany
  nfs:
    server: nfs.default.svc.cluster.local # nfs is from svc {{ include "nfs.name" .}}
    path: "/opt/shared-shibboleth-idp"
</code></pre>

<p>Description of <code>nfs service</code></p>

<pre><code>➜  helm git:(ft-helm) ✗ kubectl describe svc nfs
Name:              nfs
Namespace:         default
Labels:            app=nfs
                   chart=nfs-1.0.0
                   heritage=Tiller
Annotations:       &lt;none&gt;
Selector:          role=nfs
Type:              ClusterIP
IP:                10.19.251.72
Port:              mountd  20048/TCP
TargetPort:        20048/TCP
Endpoints:         10.16.1.5:20048
Port:              nfs  2049/TCP
TargetPort:        2049/TCP
Endpoints:         10.16.1.5:2049
Port:              rpcbind  111/TCP
TargetPort:        111/TCP
Endpoints:         10.16.1.5:111
</code></pre>

<p>And the <code>nfs deployment</code> </p>

<pre><code>➜  helm git:(ft-helm) ✗ kubectl describe replicationcontrollers telling-quoll-nfs
Name:         telling-quoll-nfs
Namespace:    default
Selector:     role=nfs
Labels:       app=nfs
              chart=nfs-1.0.0
              heritage=Tiller
Annotations:  &lt;none&gt;
Replicas:     1 current / 1 desired
Pods Status:  1 Running / 0 Waiting / 0 Succeeded / 0 Failed
Pod Template:
  Labels:  role=nfs
  Containers:
   nfs:
    Image:        k8s.gcr.io/volume-nfs:0.8
    Ports:        20048/TCP, 2049/TCP, 111/TCP
    Host Ports:   0/TCP, 0/TCP, 0/TCP
    Environment:  &lt;none&gt;
    Mounts:
      /exports from nfs (rw)
  Volumes:
   nfs:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  nfs-pv-provisioning-demo
    ReadOnly:   false
Events:         &lt;none&gt;

</code></pre>

<p>And where it is being used</p>

<pre><code>volumeMounts:
   # names must match the volume names below
   - name: RELEASE-NAME-shared-shib
     mountPath: "/opt/shared-shibboleth-idp"
;
;
volumes:
  - name: RELEASE-NAME-shared-shib
    persistentVolumeClaim:
       claimName: nfs
;
;
</code></pre>

<p>k8s <code>version</code></p>

<pre><code>➜  helm git:(ft-helm) ✗ kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-20T04:49:16Z", GoVersion:"go1.12.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.7-gke.8", GitCommit:"7d3d6f113e933ed1b44b78dff4baf649258415e5", GitTreeState:"clean", BuildDate:"2019-06-19T16:37:16Z", GoVersion:"go1.11.5b4", Compiler:"gc", Platform:"linux/amd64"}
</code></pre>

Shammir
<p>As mentioned in the comments made by <code>Patrick W</code> and <code>damitj07</code>:</p>
<p>You need have to create the folder or dir manually before try to mount, otherwise the Kubernetes will raise an error because the destination directory not exist.</p>
