stacklok / toolhive / 39881295177

73%

Build Type

push

github

Committed by web-flow

Commit Message

Classify MCPRemoteProxy pods by container readiness, not phase alone (#6765)

* Classify MCPRemoteProxy pods by container readiness, not phase alone

MCPRemoteProxy reported Ready from the pod phase alone, so a proxy pod whose
readiness probe keeps failing stayed Phase=Ready with Ready=True and the vMCP
aggregate published it as a healthy backend. The MCPServer reconciler already
classifies pods by container readiness in the same package; use that
classifier here so both CRDs report the same verdict for the same pod (#6726).

Signed-off-by: Chen Yufeiyang <fei76161@gmail.com>

* fix(operator): rank a failed remote-proxy pod above a starting one

Apply the MCPServer branch order the description promised, keep every\ndistinct failed-container reason sorted so the message is deterministic,\nand assert the status and Ready condition messages in the tests.

---------

Signed-off-by: Chen Yufeiyang <fei76161@gmail.com>
Co-authored-by: Sanskar Gurdasani <92817635+Sanskarzz@users.noreply.github.com>
Co-authored-by: Chris Burns <29541485+ChrisJBurns@users.noreply.github.com>

Coverage Stats

23 of 23 new or added lines in 1 file covered. (100.0%)

1 existing line in 1 file now uncovered.

89308 of 124541 relevant lines covered (71.71%)

127.87 hits per line