<p>I see many different Nginx implementation.</p>
<ol>
<li><p>I see some post saying stable/nginx-ingress<code>chart is deprecated, move to</code>ingress-nginx/nginx-ingress` chat.</p>
</li>
<li><p>This project <a href="https://github.com/kubernetes/ingress-nginx/releases" rel="nofollow noreferrer">https://github.com/kubernetes/ingress-nginx/releases</a> has two Nginx images <code>NGINX: 0.34.1</code> &amp; <code>ingress-nginx-2.16.0</code> what is the difference between these two images.</p>
</li>
</ol>
<p>Which Nignx Helm Chat to use for Long term support.</p>
<p>Thanks
SR</p>

<p>The <a href="https://github.com/kubernetes/ingress-nginx/tree/ingress-nginx-2.16.0/charts/ingress-nginx" rel="nofollow noreferrer">ingress-nginx-2.x.x</a> helm chart uses the <a href="https://github.com/kubernetes/ingress-nginx/blob/ingress-nginx-2.16.0/charts/ingress-nginx/values.yaml#L6-L7" rel="nofollow noreferrer">nginx-x.x.x container</a>. You don't normally need to reference the container image directly when using helm chart as that is set in the <a href="https://github.com/kubernetes/ingress-nginx/blob/ingress-nginx-2.16.0/charts/ingress-nginx/values.yaml#L6-L7" rel="nofollow noreferrer">default values</a>.</p>
<p>Helm itself moved a major version recently, from 2 -&gt; 3 which caused a lot of changes to how helm repos are structured which is why you see the &quot;deprecated&quot; message in the old Helm 2 stable repo.</p>
<p>I don't believe the ingress-nginx project has an LTS release strategy. Just use a latest 2.X release or n-1 if you want to protect yourself from unexpected changes which get thrown in occasionally.</p>
<p>NGINX (the company) do provide their own alternative <a href="https://www.nginx.com/products/nginx/kubernetes-ingress-controller/" rel="nofollow noreferrer">NGINX kubernetes-ingress</a> project if you are looking for commercial support.</p>
