I've got a GCE http(s) load balancer configured to direct traffic to 2 backends: - the default backend - a second backend with a separate host/path rule (<host>:/*)

Both backends exist on the same instance group - a container cluster running two kubernetes services that expose different NodePort.

The instance group has two named ports, one for each of the exposed NodePorts.

Despite both backends are reporting healthy, all requests to the second backend return 502.

The services themselves are not the problem - if I switch the service behind the 2nd backend to be default, it works fine.

NOTE: I've updated/simplified this description considerably since it was first posted, as I'm able to reproduce the problem with a much simpler configuration.


1 Answer 1


Traffic from the load balancer to your instance is not enabled by default. Unfortunately this is not well documented, and really, when you create a load balancer this should happen automatically.

Try adding this firewall rule the network that your load balancer and VMs are on:   tcp:1-5000   Apply to all targets
  • 1
    The issue is not the firewall rule - the services work individually. From responses in the google issue noted in OP comment, it looks like a configuration issue on the host/path rule.
    – hawkett
    Dec 15, 2015 at 0:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.