<p>I have an existing Nginx controller in my EKS cluster. This is a cluster-wide ingress controller. I want to create another Nginx controller to do some testing. This is also going to be a public-facing ingress controller. Is it possible to do that? I tried creating it by creating a new namespace and then creating new resources under that namespace but it started logging the logs for all the ingresses that were already present. Any idea on how to do that?</p>

Anshul Tripathi
<p>you need to specify the annotation<code>kubernetes.io/ingress.class: "$INGRESS_CONTROLLER"</code></p>

<p>for example here you are saying nginx will be responsible for this ingress</p>

<pre><code>kind: Ingress
metadata:
  name: foo
  annotations:
    kubernetes.io/ingress.class: "nginx"
</code></pre>

<blockquote>
  <p>if you do not define a class, your cloud provider may use a default ingress controller. 
  <a href="https://kubernetes.io/docs/concepts/services-networking/ingress-controllers/#using-multiple-ingress-controllers" rel="nofollow noreferrer">using-multiple-ingress-controllers</a></p>
</blockquote>

<p><code>alb.ingress.kubernetes.io/scheme</code> annotation is used for deciding internal or public. </p>

<p>List of <a href="https://github.com/kubernetes-sigs/aws-alb-ingress-controller/blob/master/docs/guide/ingress/annotation.md" rel="nofollow noreferrer">ingress Annotation</a> </p>
