<p>I am installing nginx ingress controller through helm chart and pods are not coming up. Got some issue with the permission.</p>
<p>Chart link - <a href="https://artifacthub.io/packages/helm/ingress-nginx/ingress-nginx" rel="nofollow noreferrer">https://artifacthub.io/packages/helm/ingress-nginx/ingress-nginx</a></p>
<p>I am using latest version 4.2.1</p>
<p>I done  debugging as stated here <a href="https://github.com/kubernetes/ingress-nginx/issues/4061" rel="nofollow noreferrer">https://github.com/kubernetes/ingress-nginx/issues/4061</a>
also tried to run as root  user <strong>runAsUser: 0</strong></p>
<p>I think i got this issue after cluster upgrade from 1.19 to 1.22. Previously it was working fine.</p>
<p>Any suggestion what i need to do to fix that?</p>
<blockquote>
<p>unexpected error storing fake SSL Cert: could not create PEM
certificate file
/etc/ingress-controller/ssl/default-fake-certificate.pem: open
/etc/ingress-controller/ssl/default-fake-certificate.pem: permission
denied</p>
</blockquote>

<p>You obviously have permission problem. Looking at the Chart you specified, the are multiple values of <code>runAsUser</code> for different config.</p>
<pre><code>controller.image.runAsUser: 101
controller.admissionWebhooks.patch.runAsUser: 2000
defaultBackend.image.runAsUser: 65534
</code></pre>
<p>I'm not sure why these are different, but if possible -</p>
<p>Try to delete your existing chart, and fresh install it.</p>
<p>If the issue still persist - check the deployment / pod events, see if the cluster alerts you about something.</p>
<p>Also worth noting, there were breaking changes in 1.22 to <code>Ingress</code> resource.
Check <a href="https://kubernetes.io/blog/2021/07/14/upcoming-changes-in-kubernetes-1-22/#what-to-do" rel="nofollow noreferrer">this</a> and this <a href="https://kubernetes.io/blog/2021/08/04/kubernetes-1-22-release-announcement/#major-changes" rel="nofollow noreferrer">links</a> from the official release notes.</p>
