Puli Kalyan Teja

> Hi, `UH` means unhealthy upstream. For egress gateway, this means the external service beyond egress gateway is unhealthy. You can use `istioctl pc endpoint istio-egressgateway-$POD_ID.istio-system |grep segment` (segement is...

> One possibility is that the envoy defaults to reusing HTTP/1.1 connections upstream, but the connection has been closed when it was reused. This case happenes intermittenly is due to...

> One possibility is that the envoy defaults to reusing HTTP/1.1 connections upstream, but the connection has been closed when it was reused. This case happenes intermittenly is due to...

> You might paste container `istio-proxy` log of curl client pod here. See also https://istio.io/latest/docs/tasks/observability/logs/access-log/#using-mesh-config to open access log. Thanks for the reply, here are SE, access log from app...

@howardjohn , Can you help me on this issue? @chaseSpace

> @howardjohn , Can you help me on this issue? @chaseSpace Hi Team, Can anyone help here? We are having more than huge clusters using wildcard model, hence need your...

> > @howardjohn , Can you help me on this issue? @chaseSpace > > Hi Team, Can anyone help here? We are having more than huge clusters using wildcard model,...

@jcmoraisjr , We need your help to resolve this issue at earliest, can you please assist. Currently, all of our 100+ haproxy applications are facing this issue.

> /start.sh permission denied Hi @jcmoraisjr , We are getting error as below when we check the logs of haproxy ingress pod. **/start.sh permission denied**

> Wondering how you're building your customized image. It seems it's working as expected when I build the image myself: > > ```shell > $ ~> cd ~/.../haproxy-ingress/ > >...