<p>Community. I need help with my config for the NFS pod in Kubernetes. I can't connect to the NFS pod. Can't understand, what a problem. Need help. I tried connecting with the command:</p>
<pre class="lang-sh prettyprint-override"><code>mount --options port=2052 --types nfs 10.110.183.188:/upload /upload
</code></pre>
<p>and get a <em><code>Connection timeout</code></em> error on my computer. When I try connecting with this command from another pod to NFS I got</p>
<pre class="lang-sh prettyprint-override"><code>mount: /upload: cannot mount 10.110.183.188:/upload read-only.
</code></pre>
<p>kubectl describe to NFS pod write this:</p>
<pre class="lang-sh prettyprint-override"><code>Serving /exports
Serving /
rpcinfo: can't contact rpcbind: : RPC: Unable to receive; errno = Connection refused
Starting rpcbind
exportfs: / does not support NFS export
NFS started
</code></pre>
<p>This is my config for NFS pod</p>
<pre class="lang-yaml prettyprint-override"><code>kind: PersistentVolume
apiVersion: v1
metadata:
  name: webpp-nfs
  labels:
    type: local
spec:
  storageClassName: manual
  capacity:
    storage: 3Gi
  accessModes:
    - ReadWriteMany
  hostPath:
    path: &quot;/mnt/webpp-data/nfs&quot;
    type: Directory
---
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: webpp-nfs
spec:
  storageClassName: manual
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 3Gi
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: webpp-upload-nfs-server
spec:
  replicas: 1
  selector:
    matchLabels:
      role: webpp-upload-nfs-server
  template:
    metadata:
      labels:
        role: webpp-upload-nfs-server
    spec:
      containers:
      - name: webpp-upload-nfs-server
        image: gcr.io/google_containers/volume-nfs:latest
        ports:
          - name: nfs
            containerPort: 2052
          - name: mountd
            containerPort: 32771
        securityContext:
          privileged: true
        volumeMounts:
          - mountPath: /exports
            name: storage
      nodeSelector:
        env: stateful
      volumes:
        - name: storage
          persistentVolumeClaim:
            claimName: webpp-nfs
---
apiVersion: v1
kind: Service
metadata:
  name: webpp-upload-nfs-server
spec:
  ports:
    - name: nfs
      port: 2052
      nodePort: 2052
    - name: mountd
      port: 32771
      nodePort: 32771
  type: NodePort
  selector:
    role: webpp-upload-nfs-server
</code></pre>
<p>This is a config for the pod to connect to NFS</p>
<pre class="lang-yaml prettyprint-override"><code>apiVersion: apps/v1
kind: Deployment
metadata:
  name: $CI_ENVIRONMENT_SLUG-webpp-$CI_COMMIT_REF_SLUG
spec:
  selector:
    matchLabels:
      app: webpp-$CI_COMMIT_REF_SLUG
  replicas: 1
  template:
    metadata:
      labels:
        app: webpp-$CI_COMMIT_REF_SLUG
    spec:
      nodeSelector:
        env: apps
      containers:
      - name: nginx-$CI_COMMIT_REF_SLUG
        image: nginx:latest
        ports:
         - containerPort: 80
        volumeMounts:
        - name: shared-files
          mountPath: /app
        - mountPath: /etc/nginx/conf.d/default.conf
          name: nginx-config
          subPath: s1-kube.conf

      - name: app-$CI_COMMIT_REF_SLUG
        image: git.webpp.ru:4567/webpp/webpp:$CI_COMMIT_REF_SLUG
        ports:
        - containerPort: 9000
        imagePullPolicy: Always
        volumeMounts:
        - mountPath: /upload
          name: upload
        lifecycle:
          postStart:
            exec:
              command: [&quot;bash&quot;, &quot;/start.sh&quot;]

      imagePullSecrets:
        - name: git.webpp.ru
      volumes:
        - name: shared-files
          emptyDir: {}
        - name: nginx-config
          configMap:
            name: nginx-$CI_COMMIT_REF_SLUG
        - name: upload
          persistentVolumeClaim:
            claimName: webpp-nfs
---
apiVersion: v1
kind: Service
metadata:
  name: webpp-$CI_COMMIT_REF_SLUG
  labels:
    app: webpp-$CI_COMMIT_REF_SLUG
spec:
  ports:
  - port: 80
    protocol: TCP
  selector:
    app: webpp-$CI_COMMIT_REF_SLUG
---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: webpp-$CI_COMMIT_REF_SLUG
  annotations:
    nginx.ingress.kubernetes.io/proxy-buffers: &quot;50m&quot;
    nginx.ingress.kubernetes.io/proxy-buffer-size: &quot;50m&quot;
    nginx.ingress.kubernetes.io/proxy-body-size: &quot;50m&quot;
    nginx.ingress.kubernetes.io/proxy-busy-buffers-size: &quot;50m&quot;
spec:
  rules:
  - host: $CI_COMMIT_REF_SLUG.webpp.wpp.zone
    http:
      paths:
      - path: &quot;/&quot;
        backend:
          serviceName: webpp-$CI_COMMIT_REF_SLUG
          servicePort: 80
</code></pre>
<p>svc for pods look like this</p>
<pre><code>NAME                      TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                         AGE
webpp-db-service          NodePort    10.100.169.28    &lt;none&gt;        3306:3304/TCP                   347d
webpp-develop             ClusterIP   10.101.10.54     &lt;none&gt;        80/TCP                          8h
webpp-feature-2334        ClusterIP   10.102.208.56    &lt;none&gt;        80/TCP                          9h
webpp-upload-nfs-server   NodePort    10.110.183.188   &lt;none&gt;        2052:2052/TCP,32771:32771/TCP   255d
</code></pre>
<p>Pods seem like this</p>
<pre class="lang-yaml prettyprint-override"><code>NAME                                                           READY   STATUS    RESTARTS   AGE
review-develop-3zknud-webpp-develop-754d56c654-v8hwx           0/2     Pending   0          8h
review-feature-23-3smwjk-webpp-feature-2334-695959494f-4hgfj   2/2     Running   0          7h43m
webpp-db-769757b69c-kh4c4                                      1/1     Running   6          41d
webpp-upload-nfs-server-594c6fbb6d-c2r22                       1/1     Running   0          7h45m
</code></pre>
<p>I tried connect from pod <em><code>review-feature-23-3smwjk-webpp-feature-2334-695959494f-4hgfj</code></em> to nfs pod <em><code>webpp-upload-nfs-server-594c6fbb6d-c2r22</code></em>.</p>

<blockquote>
<p><em><code>mount --options port=2052 --types nfs 10.110.183.188:/upload /upload</code></em></p>
</blockquote>
<p>There might a firewall preventing you from reaching port <code>2052</code>. Just as an FYI if you are running NFSv4 the ports to be <a href="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/storage_administration_guide/s2-nfs-nfs-firewall-config" rel="nofollow noreferrer">allowed</a> are <code>111</code> and <code>2049</code></p>
<blockquote>
<p>*<code>mount: /upload: cannot mount 10.110.183.188:/upload read-only</code>.</p>
</blockquote>
<p>This is more of a misnomer:</p>
<pre class="lang-sh prettyprint-override"><code>rpcinfo: can't contact rpcbind: : RPC: Unable to receive; errno = Connection refused
</code></pre>
<p>It really looks like /upload is not exported in your <code>webpp-upload-nfs-server</code> container.</p>
<p>I checked the image and it looks good in its file system:</p>
<pre class="lang-sh prettyprint-override"><code>/exports *(rw,fsid=0,insecure,no_root_squash)
/ *(rw,fsid=0,insecure,no_root_squash)
</code></pre>
<p>You are trying the mount from <code>NFS:/uploads</code> but you are exporting <code>NFS:/exports</code>. So you can try:</p>
<pre class="lang-sh prettyprint-override"><code>mount --options port=2052 --types nfs 10.110.183.188:/exports /upload
</code></pre>
<p>✌️</p>
