You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm following the video and example but setting up ingress shows different behaviour than what's shown in the video.
Day3 - Deploy first app with ingress brings up the hostname (FQDN) but it does not route the app using 80. (default-backend 404 error). I tested using the actual port, it successfully opens up the page.
A few thing I found is that no ip assigned to default-http-backend and nginx-ingres-controller external IP shows as pending. Also log indicates "No Cloud provide tag"
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
first-app NodePort 10.101.234.166 80:32394/TCP 84m
nginx-ingress-controller LoadBalancer 10.98.224.237 80:32262/TCP,443:31916/TCP 13h
nginx-ingress-default-backend ClusterIP 10.96.91.205 80/TCP 13h
E0422 23:19:43.017582 1 core.go:77] Failed to start service controller: WARNING: no cloud provider provided, services of type LoadBalancer will fail
After some research, I found LB might not be available in custom cluster like this but wonder if it's some configuration I screwed up or any additional steps to be done which not included during the course.
The text was updated successfully, but these errors were encountered:
I also want to mention this is a great course!
I'm following the video and example but setting up ingress shows different behaviour than what's shown in the video.
Day3 - Deploy first app with ingress brings up the hostname (FQDN) but it does not route the app using 80. (default-backend 404 error). I tested using the actual port, it successfully opens up the page.
A few thing I found is that no ip assigned to default-http-backend and nginx-ingres-controller external IP shows as pending. Also log indicates "No Cloud provide tag"
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
first-app NodePort 10.101.234.166 80:32394/TCP 84m
nginx-ingress-controller LoadBalancer 10.98.224.237 80:32262/TCP,443:31916/TCP 13h
nginx-ingress-default-backend ClusterIP 10.96.91.205 80/TCP 13h
E0422 23:19:43.017582 1 core.go:77] Failed to start service controller: WARNING: no cloud provider provided, services of type LoadBalancer will fail
After some research, I found LB might not be available in custom cluster like this but wonder if it's some configuration I screwed up or any additional steps to be done which not included during the course.
The text was updated successfully, but these errors were encountered: