<p>Helo guys I'd like some help with an issue :
I'm using a kubernetes cluster that is provided to me by rancher (so I did not configured it)</p>
<p>but it has an nginx ingress controller :</p>
<pre><code> kubectl -n ingress-nginx get all -o wide
NAME                                        READY   STATUS    RESTARTS   AGE   IP               NODE                           NOMINATED NODE   READINESS GATES
pod/default-http-backend-598b7d7dbd-fgpns   1/1     Running   3          48d   192.168.121.64   pr-k8s-fe-fastdata-worker-02   &lt;none&gt;           &lt;none&gt;
pod/nginx-ingress-controller-72d8s          1/1     Running   0          6d    172.34.10.123    pr-k8s-fe-fastdata-worker-03   &lt;none&gt;           &lt;none&gt;
pod/nginx-ingress-controller-rn4fw          1/1     Running   0          6d    172.34.10.192    pr-k8s-fe-fastdata-worker-01   &lt;none&gt;           &lt;none&gt;
pod/nginx-ingress-controller-v2m8b          1/1     Running   0          6d    172.34.10.173    pr-k8s-fe-fastdata-worker-02   &lt;none&gt;           &lt;none&gt;

NAME                           TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE   SELECTOR
service/default-http-backend   ClusterIP   192.168.33.89   &lt;none&gt;        80/TCP    48d   app=default-http-backend

NAME                                      DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE   CONTAINERS                 IMAGES                                                   SELECTOR
daemonset.apps/nginx-ingress-controller   3         3         3       3            3           &lt;none&gt;          48d   nginx-ingress-controller   rancher/nginx-ingress-controller:nginx-0.35.0-rancher1   app=ingress-nginx

NAME                                   READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS             IMAGES                                                         SELECTOR
deployment.apps/default-http-backend   1/1     1            1           48d   default-http-backend   rancher/nginx-ingress-controller-defaultbackend:1.5-rancher1   app=default-http-backend

NAME                                              DESIRED   CURRENT   READY   AGE   CONTAINERS             IMAGES                                                         SELECTOR
replicaset.apps/default-http-backend-598b7d7dbd   1         1         1       48d   default-http-backend   rancher/nginx-ingress-controller-defaultbackend:1.5-rancher1   app=default-http-backend,pod-template-hash=598b7d7dbd

</code></pre>
<p>and as I'm watching a video tutorial ( <a href="https://www.youtube.com/watch?v=KnOZwxvxfnA" rel="nofollow noreferrer">[ Kube 59.1 ] Nginx Ingress in Kubernetes Revisited</a>) <strong>I noticed that he when he display all like me alongside the default backen svc in the ingress namespace he also has an &quot;ingress-controller svc of type load balancer&quot; and I don't, so how can I rectify that ?</strong>
thank you for your help .</p>

Ait Zaid
<p>So I managed to make it work , the nginx that was on my rancher was deployed from the rancher app catalogue, and the field &quot;deploy a service&quot; was set to false, so I upgraded it and put the field to true and it deployed me the load balancing service so now it's working fine.
Thank you</p>
