Istio Ingress resulting in "no healthy upstream"

kubernetes istio
Pegladon picture Pegladon · Dec 6, 2017 · Viewed 23.9k times · Source

I am using deploying an outward facing service, that is exposed behind a nodeport and then an istio ingress. The deployment is using manual sidecar injection. Once the deployment, nodeport and ingress are running, I can make a request to the istio ingress.

For some unkown reason, the request does not route through to my deployment and instead displays the text "no healthy upstream". Why is this, and what is causing it?

I can see in the http response that the status code is 503 (Service Unavailable) and the server is "envoy". The deployment is functioning as I can map a port forward to it and everything works as expected.

Answer

Malathi picture Malathi · May 29, 2019

I faced the issue, when I my pod was in ContainerCreating state. So, it resulted in 503 error. Also as @pegaldon, explained it can also occur due to incorrect route configuration or there are no gateways created by user.

Related questions

How does Istio compare to Traefik?

Traefik is a reverse HTTP proxy with several supported backends, Kubernetes included. How does Istio compare?

Read More
Readiness probe failed: HTTP probe failed with statuscode: 503 in ISTIO

I have deployed istio service mesh in my AKS cluster. i have ui and backend services both configured in istio for service communication. i am able to invoke backend service through istio, and no problem in accessing my backend services. …

Read More
How to fix 'container runtime is down,PLEG is not healthy'

I have aks with one kubernetes cluster having 2 nodes. Each node has about 6-7 pod running with 2 containers for each pod. One container is my docker image and the other is created by istio for its service mesh. But after …

Read More