<p>ingress-nginx-controller-6bf7bc7f94-ml4js looks like a pod. Pods are not containers but they can contain containers. Why don't you describe it and see what containers it contains.</p>

CC BY-SA 4.0
2022-08-04T05:27:50.433Z
It shows only the `controller` container, so the pod contains just one container. The other 2 are not present.
newby88
CC BY-SA 4.0
2022-08-04T01:38:02.647Z
2022-08-04T01:38:02.647Z
Levi
<p>Did you include the line that said there should be two replicas?</p>
<blockquote>
<p>For added redundancy, two replicas of the NGINX ingress controllers are deployed with the <code>--set controller.replicaCount</code> parameter. To fully benefit from running replicas of the ingress controller, make sure there's more than one node in your AKS cluster.</p>
</blockquote>

CC BY-SA 4.0
2022-08-09T21:05:31.267Z
2022-08-09T21:05:31.267Z
chicks
<p>I'm trying to get a feel for the Kubernetes Nginx ingress controller. Trying to deploy it to an AKS cluster, however I can't figure out the following. According to <a href="https://docs.microsoft.com/en-us/azure/aks/ingress-basic?tabs=azure-cli" rel="nofollow noreferrer">Create an ingress controller in Azure Kubernetes Service (AKS)</a></p>
<p><code>To control image versions, you'll want to import them into your own Azure Container Registry. The NGINX ingress controller Helm chart relies on three container images. Use az acr import to import those images into your ACR.</code></p>
<p>So, I've pulled, tagged and pushed the controller, patch and default backend images to ACR.</p>
<p>Next, did <code>helm show values ingress/nginx/ingress-nginx &gt; values.yaml</code> and created a new <code>.yaml</code> to reference it a installation time (so that it can grab the images from ACR rather than the default repo).</p>
<p>However, after install I'm surprised to find only 1 pod related to nginx</p>
<pre><code>NAME                                           READY   STATUS    RESTARTS   AGE
ingress-nginx-controller-764784f688-qbbq8      1/1     Running   0          49m
</code></pre>
<p>I've even tried to install it with the defaults without providing my own <code>.yaml</code> with <code>-f foo.yaml</code> like this:</p>
<pre><code> helm upgrade --install ingress-nginx ingress-nginx   --repo https://kubernetes.github.io/ingress-nginx   --namespace ingress-nginx --create-namespace
</code></pre>
<p>But still only 1 pod:</p>
<pre><code>NAME                                        READY   STATUS    RESTARTS   AGE
ingress-nginx-controller-6bf7bc7f94-ml4js   1/1     Running   0          55s
</code></pre>
<p>Per my understanding this is what gets created:
<a href="https://i.sstatic.net/brvuf.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/brvuf.png" alt="controller" /></a></p>
<p><a href="https://i.sstatic.net/bR4Nl.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/bR4Nl.png" alt="patch" /></a></p>
<p><a href="https://i.sstatic.net/Z8FVs.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Z8FVs.png" alt="default" /></a></p>
<p>What am I missing please ?</p>

CC BY-SA 4.0
2022-08-04T18:15:15.847Z
I think you should open a git issue in the helm charts repo.
Levi
CC BY-SA 4.0
2023-01-10T16:33:00.340Z
How do you check ? `kubectl get po -A | grep nginx` ?
Tensibai
<kubernetes><kubernetes-helm><ingress-nginx>
kubernetes nginx ingress confusion
newby88
# kubernetes nginx ingress confusion

(Asked by: username_0 on 2022-08-03)

I'm trying to get a feel for the Kubernetes Nginx ingress controller. Trying to deploy it to an AKS cluster, however I can't figure out the following. According to Create an ingress controller in Azure Kubernetes Service (AKS)
To control image versions, you'll want to import them into your own Azure Container Registry. The NGINX ingress controller Helm chart relies on three container images. Use az acr import to import those images into your ACR.
So, I've pulled, tagged and pushed the controller, patch and default backend images to ACR.
Next, did helm show values ingress/nginx/ingress-nginx > values.yaml and created a new .yaml to reference it a installation time (so that it can grab the images from ACR rather than the default repo).
However, after install I'm surprised to find only 1 pod related to nginx
NAME                                           READY   STATUS    RESTARTS   AGE
ingress-nginx-controller-764784f688-qbbq8      1/1     Running   0          49m

I've even tried to install it with the defaults without providing my own .yaml with -f foo.yaml like this:
 helm upgrade --install ingress-nginx ingress-nginx   --repo https://kubernetes.github.io/ingress-nginx   --namespace ingress-nginx --create-namespace

But still only 1 pod:
NAME                                        READY   STATUS    RESTARTS   AGE
ingress-nginx-controller-6bf7bc7f94-ml4js   1/1     Running   0          55s

Per my understanding this is what gets created:



What am I missing please ?

**Tags:** kubernetes, kubernetes-helm, ingress-nginx

> **Comments:**
> **username_1**: I think you should open a git issue in the helm charts repo.  
> **username_2**: How do you check ? `kubectl get po -A | grep nginx` ?  

---

## 2 answers

### Answer by username_1 on 2022-08-04. Score: 0

ingress-nginx-controller-6bf7bc7f94-ml4js looks like a pod. Pods are not containers but they can contain containers. Why don't you describe it and see what containers it contains.

> **Comments:**
> **username_0**: It shows only the `controller` container, so the pod contains just one container. The other 2 are not present.  

---

### Answer by username_3 on 2022-08-09. Score: 0

Did you include the line that said there should be two replicas?

> For added redundancy, two replicas of the NGINX ingress controllers are deployed with the `--set controller.replicaCount` parameter. To fully benefit from running replicas of the ingress controller, make sure there's more than one node in your AKS cluster.


---

