Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ingress controller with k8s multi node cluster #2

Open
charlseo opened this issue Apr 23, 2019 · 0 comments
Open

Ingress controller with k8s multi node cluster #2

charlseo opened this issue Apr 23, 2019 · 0 comments

Comments

@charlseo
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant