No upstream for LoadBalancer type services

[zihaoyu]

Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.): No

What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): LoadBalancer

---

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

NGINX Ingress controller version:
0.9.0-beta.11

Kubernetes version (use kubectl version):
1.7.6

Environment:

• Cloud provider or hardware configuration: AWS
• OS (e.g. from /etc/os-release): Container Linux by CoreOS 1465.8.0 (Ladybug)
• Kernel (e.g. uname -a): Linux ip-10-72-32-26.us-west-2.compute.internal 4.12.14-coreos Basic structure  #1 SMP Wed Sep 20 22:20:05 UTC 2017 x86_64 Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz GenuineIntel GNU/Linux
• Install tools:
• Others:

What happened:
My service has ingress defined, and also service type LoadBalancer. When I hit the ingress controller with the hostname defined in ingress resource, I get 503. Upon inspecting the nginx conf file, I see that the upstream definition for that service is empty:

    upstream production-blackforest-80 {
        # Load balance algorithm; empty for round robin, which is the default
        least_conn;
        server 127.0.0.1:8181 max_fails=0 fail_timeout=0;
    }

It looks like this only happens to LoadBalancer type. NodePort and ClusterIP services have their pod IPs in upstreams.

What you expected to happen:

I can hit my service via ingress.

How to reproduce it (as minimally and precisely as possible):

1. Create a service with type LoadBalancer.
2. Create an ingress rule for the service.
3. Hit the ingress controller with the hostname defined in ingress rule.

Anything else we need to know:

[aledbf]

Closing. Services of type=LoadBalancer are not valid. You need to use a normal service.