<p>I have deployed EFS file system in AWS EKS cluster after the deployment my storage pod is up and running.</p>
<pre><code>kubectl get pod -n storage
NAME                                     READY   STATUS    RESTARTS   AGE
nfs-client-provisioner-968445d79-g8wjr   1/1     Running   0          136m
</code></pre>
<p>When I'm trying deploy application pod is not not coming up its pending state <code>0/1</code> at the same time  PVC is not bounded its pending state.</p>
<p>Here are the logs for after the actual application deployment.</p>
<pre><code>I0610 13:26:11.875109       1 controller.go:987] provision &quot;default/logs&quot; class &quot;efs&quot;: started
E0610 13:26:11.894816       1 controller.go:1004] provision &quot;default/logs&quot; class &quot;efs&quot;: unexpected error getting claim reference: selfLink was empty, can't make reference

</code></pre>
<p>I'm using k8 version 1.20 could you please some one help me on this.</p>

<p>Kubernetes <em>1.20</em> stopped propagating <code>selfLink</code>.<br />
There is a <a href="https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/issues/25#issuecomment-742616668" rel="nofollow noreferrer">workaround</a> available, but it does not always work.</p>
<p>After the lines</p>
<pre><code>spec:
  containers:
  - command:
    - kube-apiserver
</code></pre>
<p>add</p>
<pre><code>- --feature-gates=RemoveSelfLink=false
</code></pre>
<p>then reapply API server configuration</p>
<pre><code>kubectl apply -f /etc/kubernetes/manifests/kube-apiserver.yaml
</code></pre>
<p>This workaround will not work after version <em>1.20</em> (1.21 and up), as <code>selfLink</code> will be completely removed.</p>
<hr />
<p>Another solution is to use newer NFS provisioner image:<br />
<code>gcr.io/k8s-staging-sig-storage/nfs-subdir-external-provisioner:v4.0.0</code></p>
