You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Non-leader instances returns false on readiness probes. If a deployment has multiple instances, it can never be seen as "ready" in some CI/CD systems (like ArgoCD) . Since the validation webhook is migrated to CELs in KGO 1.5, there are no exposed services that requires the traffic to be only sent to the leader, we can enable the readiness probed of non-leader instances.
Proposed Solution
Start the readiness probe service on both leader and non-leader instances.
...
Additional Information
...
Acceptance Criteria
Leader and non-leader instances are all in ready state after started
The text was updated successfully, but these errors were encountered:
Problem Statement
Non-leader instances returns
false
on readiness probes. If a deployment has multiple instances, it can never be seen as "ready" in some CI/CD systems (like ArgoCD) . Since the validation webhook is migrated to CELs in KGO 1.5, there are no exposed services that requires the traffic to be only sent to the leader, we can enable the readiness probed of non-leader instances.Proposed Solution
Start the readiness probe service on both leader and non-leader instances.
...
Additional Information
...
Acceptance Criteria
ready
state after startedThe text was updated successfully, but these errors were encountered: