Istio No Healthy Upstream Return

Listing Websites about Istio No Healthy Upstream Return

Filter Type:

Troubleshooting "no healthy upstream" errors in Istio …

(1 days ago) A "no healthy upstream" error can be caused by Istio, a misconfigured network device, or actual network outages. Thus, it is difficult for the mesh operations team to pinpoint the cause or even predict its occurrence, because … See more

https://developers.redhat.com/articles/2022/12/23/troubleshooting-no-healthy-upstream-errors-istio-service-mesh

Category:  Health Show Health

Istio Ingress resulting in "no healthy upstream"

(1 days ago) WebThe 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 …

https://stackoverflow.com/questions/47664397/istio-ingress-resulting-in-no-healthy-upstream

Category:  Health Show Health

"no healthy upstream" error istio routing rule issue

(5 days ago) WebIn this GitHub issue on the Istio project, you can try and go through the checklist in the issue description to verify that the service components are functional.. …

https://stackoverflow.com/questions/72891458/no-healthy-upstream-error-istio-routing-rule-issue

Category:  Health Show Health

no healthy upstream being returned when service is …

(3 days ago) WebSteps to reproduce the bug. Install Istio 1.6.8 (also fails with 1.7.4) Deploy sample bookinfo app and gateway and ensure it is available. Deploy console app in k8s. Configure gw/vs …

https://github.com/istio/istio/issues/29254

Category:  Health Show Health

Intermittently "no healthy upstream" being returned - Discuss Istio

(1 days ago) WebHi Team we are having Kubernetes cluster version 1.23.8 and Istio version 1.14.5 Some time after the application deployment application gives 503 “no healthy …

https://discuss.istio.io/t/intermittently-no-healthy-upstream-being-returned-when-service-is-available-istiod-restarts-fixing-the-issue/15052

Category:  Health Show Health

Istio / Traffic Management Problems

(4 days ago) WebNR: No route configured, check your DestinationRule or VirtualService. UO: Upstream overflow with circuit breaking, check your circuit breaker configuration in DestinationRule. …

https://istio.io/latest/docs/ops/common-problems/network-issues/

Category:  Health Show Health

Istio Give 503 error with no healthy upstream when pods get evicted

(9 days ago) WebHi Framled, I didn’t have the fix from istio but I can help you with the work around I did. When issue occurs, recreate virtualservice for the application.

https://discuss.istio.io/t/istio-give-503-error-with-no-healthy-upstream-when-pods-get-evicted/6069

Category:  Health Show Health

Istio / Health Checking of Istio Services

(9 days ago) WebTo confirm that the liveness probes are working, check the status of the sample pod to verify that it is running. $ kubectl -n istio-io-health get pod NAME READY STATUS …

https://istio.io/latest/docs/ops/configuration/mesh/app-health-check/

Category:  Health Show Health

Headless service broken in 1.6.0 (no healthy upstream) #24082

(3 days ago) WebUpgrading from 1.5.4 to 1.6.0 resulted in "no healthy upstream" errors from Envoy. then a DNS lookup for the kube service will return all of the pod IPs. Assume …

https://github.com/istio/istio/issues/24082

Category:  Health Show Health

Istio-Proxy returning UH / no healthy upstream at startup for …

(3 days ago) WebOur assumption is - Given the large amount of STRICT_DNS clusters, istio-proxy is taking time to complete the DNS resolution, and until then it doesn't show the endpoints for …

https://github.com/istio/istio/issues/48692

Category:  Health Show Health

Network Problems - Istio

(2 days ago) WebNetwork Problems. 9 minute read. Requests are rejected by Envoy. Route rules don’t seem to affect traffic flow. Destination rule policy not activated. 503 errors after setting …

https://istio.io/v1.3/docs/ops/troubleshooting/network-issues/

Category:  Health Show Health

503 errors even when pod is healthy - Discuss Istio

(7 days ago) WebWe faced a weird situation recently when out of 3 replicas of a service 1 pod was returning 503 “no healthy upstream error” for any request routed to it. On further …

https://discuss.istio.io/t/503-errors-even-when-pod-is-healthy/6430

Category:  Health Show Health

All sidecars reported 503 “ no healthy upstream - GitHub

(3 days ago) WebDescribe the bug {{ Succinctly describe the bug }} the istio cluster run well for serveral days, however yesterday all sidecar report 503 error"no healthy upstream" …

https://github.com/istio/istio/issues/10515

Category:  Health Show Health

Isto 503 no healthy upstream after pod killed - Discuss Istio

(7 days ago) WebWe are using Istio 1.5.4 and have started using a headless service to get direct pod to pod communication working with Istio mTLS. This is all working fine, but we …

https://discuss.istio.io/t/isto-503-no-healthy-upstream-after-pod-killed/9280

Category:  Health Show Health

ServiceEntry - "no healthy upstream" error · Issue #38996 · istio/istio

(3 days ago) WebBut a "no healthy upstream" was a challenging start to finding this "root cause". 🚧 This issue or pull request has been closed due to not having had activity from …

https://github.com/istio/istio/issues/38996

Category:  Health Show Health

Retry is not working when scaling pods to 0 - Discuss Istio

(6 days ago) WebRetry configurations are not working as I tried scaling the pods to 0 using the command kubectl scale --replicas=0. Checked the logs of the istio-ingressgateway pod, …

https://discuss.istio.io/t/retry-is-not-working-when-scaling-pods-to-0/14450

Category:  Health Show Health

Filter Type: