Details
-
Bug
-
Resolution: Done
-
Blocker
-
OSSM 2.2.4, OSSM 2.3.0
-
None
-
False
-
None
-
False
-
https://github.com/maistra/xns-informer/pull/43, https://github.com/maistra/xns-informer/pull/42, https://github.com/maistra/xns-informer/pull/40, https://github.com/maistra/xns-informer/pull/35, https://github.com/maistra/api/pull/42, https://github.com/maistra/api/pull/43, https://github.com/maistra/api/pull/44, https://github.com/maistra/api/pull/45, https://github.com/maistra/istio/pull/726, https://github.com/maistra/istio/pull/727, https://github.com/maistra/istio/pull/728, https://github.com/maistra/istio/pull/729
Description
*Note: this is a public-facing duplicate of OSSM-2419.
Sometimes, especially when the mesh contains many member namespaces, the Istiod pod fails to become ready (the container's readiness probe fails with "Connection refused").
On first glance, the Istiod log seems to indicate that everything is up and running, since it contains lines indicating that xDS pushes are being performed. However, not all components within the server are actually running (we know this because the following line is missing: "All caches have been synced up in 123s, marking server ready").
You can find more information in the RedHat internal Jira issue OSSM-2419 (which can't be made public because it contains customer data).