4

I am doing with k8s and Istio as service meshing. I wonder what if pod in a service A is not ready(Readiness is unhealthy), How Istio will treat this pod? Is there way i can config rule of load balance(Load balance at L3/L4 layer)?

Blind
  • 99
  • 1
  • 11

1 Answers1

3

You might want to check Health Checking of Istio Services to check the health of your pods. As mentioned in the post, you would have to configure the containers with liveness probes using kubectl before you can actually do health checking.

CyG
  • 136
  • 4
  • I've read this document. But in this [document](https://istio.io/latest/docs/concepts/traffic-management/) said: _"By default, the Envoy proxies distribute traffic across each service’s load balancing pool using a round-robin model, where requests are sent to each pool member in turn, returning to the top of the pool once each service instance has received a request"_. Istio will remove **unhealthy pod** to Load Balancing pool. But long live connection(TCP, gRPC) will be still keep? – Blind Oct 29 '20 at 04:42
  • I've tested this case. Long live connection still keeping. But i wonder how Istio can do it? – Blind Oct 29 '20 at 04:47
  • 3
    I read that document several time but I must say it is very poorly documented till date. Its starts with top level concept without explaining what are Rewrite Probes. Why HTTP probes need to be rewritten. Woo rewrites HTTP probes ? – bhantol Jul 26 '21 at 18:34