Lab 11.2 step 6 - Ingress controller service never starts

trevski

Ingress service never appears:

$ kubectl get ingress --all-namespaces
No resources found

LoadBalancer service never goes beyond pending:

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
myingress-ingress-nginx-controller LoadBalancer 10.106.214.23 <pending> 80:31109/TCP,443:32503/TCP 4m57s app.kubernetes.io/component=controller,app.kubernetes.io/instance=myingress,app.kubernetes.io/name=ingress-nginx

No pods are found if I
kubectl get pods -n default | grep nginx

I have tried the creation twice. After the first time I cleaned all the resources out of ingress-nginx and tried again. Same result. Any advice please?

chrispokorni

Hi @trevski,

Based on the output you provided, the "No resources found" message is expected at step 6, since the Ingress object has not been created just yet. Steps 7 and 8 will allow you to inspect the Ingress manifest and then create the Ingress object respectively.

The LoadBalancer Service appears to be in the expected state. The "<pending>" field only refers to the External-IP address of the Service. According to a much earlier lab exercise, the LoadBalancer Service type in the lab environment is not paired with a load balancer and does not display an external IP address.

In step 4 of lab exercise 11.2, did you properly declare the kind as DaemonSet in the values.yaml manifest? It may be at a different line than the one suggested, and it is case sensitive.

After the ingress controller release is installed through the helm CLI (step 5), run kubectl get ds to list all DaemonSets. If it does not show the "myingress-ingress-nginx-controller" DaemonSet, then you need to revisit step 4 to correct the values.yaml manifest of the ingress-nginx Chart.

Regards,
-Chris

trevski

Thanks Chris! You were right on the money - I had the case of DaemonSet incorrect