do you mean in 1.5 alpha “15020/healthz/ready” readiness probe is changed?
what i observed is that envoy gets added into k8 service before it receives the listener config from pilot, client gets connection refused for ~1 second when envoy doesn’t have listener ready.
--applicationPorts option (via helm’s applicationPorts variable) to pilot agent, envoy becomes ready only when it has all the listeners mentioned in
applicationPorts are ready.
I verified this by using some non configured listener port, then envoy pod wasn’t ready because readiness probe 15020/healthz/ready was giving 503.
thats why this option is useful unless there is some other method implemented to achieve the same in 1.5 alpha.