docker – K8S ingress-nginx EXTERNAL_IP remains forever

We use local K8S cluster for development in our company and the first step after fresh install (or reset) of K8S is to install ingress-nginx/ingress-nginx of version 3.34.0 and wait for it to have EXTERNAL_IP to be set to localhost. It’s ok for my colleagues, but for me it’s stuck forever in <pending> state like this:

$ kubectl get all
NAME                                            READY   STATUS    RESTARTS   AGE
pod/ingress-nginx-controller-5f6d7594cd-whlp4   1/1     Running   0          5m30s

NAME                                         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
service/ingress-nginx-controller             LoadBalancer   <pending>     80:30701/TCP,443:30433/TCP   5m30s
service/ingress-nginx-controller-admission   ClusterIP   <none>        443/TCP                      5m30s
service/kubernetes                           ClusterIP       <none>        443/TCP                      6m57s

NAME                                       READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/ingress-nginx-controller   1/1     1            1           5m30s

NAME                                                  DESIRED   CURRENT   READY   AGE
replicaset.apps/ingress-nginx-controller-5f6d7594cd   1         1         1       5m30s

And it has been so for hours, almost a day. Tried resetting cluster, restarting Docker, different versions of ingress-nginx, restarting mac – no use. It must have this external ip, otherwise when we deploy our application locally, we can’t access it.

OS: macOS Ventura 13.2.1 (arm, m2)

Docker version:
enter image description here

Read more here: Source link