<p>Is it possible to run multiple IngressController in the same Namespace with the same IngressClass?</p>
<p>I have multiple IngressController with different LoadBalancer IP Addresses and would like to continue with this setup.</p>
<p>I upgraded the first IngressController to the latest version.
Updating the second/third/.. IngressController fails because of:</p>
<pre class="lang-sh prettyprint-override"><code>rendered manifests contain a resource that already exists. Unable to continue with update: IngressClass &quot;nginx&quot; in namespace &quot;&quot; exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key &quot;meta.helm.sh/release-name&quot; must equal &quot;nginx-ingress-lb-02&quot;: current value is &quot;nginx-ingress-lb-01&quot;
</code></pre>
<p>Any idea how to fix this?</p>

sokolata
<p>The issue you mention here is mainly with Helm, preventing you from overwriting some resources - your IngressClass - that belongs to another helm deployment.</p>
<p>One way to work around this may be to use helm &quot;--dry-run&quot; option. Once you have the list of objects written into a file: remove the IngressClass, then apply that file.</p>
<p>Another way may be to patch the chart deploying your controller. As a contributor to the Traefik helm chart, I know that we would install IngressClasses named after the Traefik deployment we operate. The chart you're using, for Nginx, apparently does not implement support for that scenario. Which doesn't mean it shouldn't work.</p>
<p>Now, answering your first question, is it possible to run multiple IngressController in the same Namespace with the same IngressClass: yes.</p>
<p>You may have several Ingress Controllers, one that watches for Ingresses in namespace A, another in namespace B, both ingresses referencing the same class. Deploying those ingresses into the same namespace is possible - although implementing NetworkPolicies, isolating your controllers into their own namespace would help in distinguishing who's who.</p>
