A message for Linux.com registered users: We are in the process of making changes to the Linux forums. Starting Monday, 8/13/18 at 6:00 PM PT, you will be unable to access the forums. They will re-launch as soon as possible on Wednesday, 8/15/18 with new features and improved functionality. Thank you for your patience and stay tuned for the new improved forums.

November 30, 2017

nginx-ingress-controller CrashLoopBackOff (Lab 9)

Hi All,

When I use multi cluster nodes (e.g. 1 master and 1 worker node), I’m getting the following error with the nginx-ingress-controller Pod:


$ kubectl get po -w

NAME                                                 READY     STATUS 

nginx-ingress-controller-p86r8  1/1       Running

nginx-ingress-controller-p86r8   0/1       Error     

nginx-ingress-controller-p86r8   0/1       CrashLoopBackOff

nginx-ingress-controller-p86r8   1/1       Running

nginx-ingress-controller-p86r8   0/1       Error

nginx-ingress-controller-p86r8   0/1       CrashLoopBackOff


$ kubectl get po,rc,svc

NAME                                                  READY     STATUS

po/default-http-backend-29mvr       1/1       Running

po/nginx-ingress-controller-p86r8   0/1       Error


NAME                                       DESIRED   CURRENT   READY

rc/default-http-backend        1                   1                 1

rc/nginx-ingress-controller   1                   1                 1


NAME                                     TYPE          CLUSTER-IP     EXTERNAL-IP   PORT(S)

svc/default-http-backend   ClusterIP   <none>           80/TCP

svc/kubernetes                     ClusterIP          <none>          443/TCP



I’m using the backend.yaml manifest provided in Lab9.

(I have to mention that the Pod-to-Pod network has been configured with Weave Net add-on and all works fine. So, I don’t think the issue is related to Weave Net).


However, when using minikube all works fine.


Does anyone had the same issue? Any solution?




Click Here!