stacklok / toolhive / 23859528017

65%

Build Type

push

github

Committed by web-flow

Commit Message

Add top-level Ready condition to MCPServer (#4477)

* Add top-level Ready condition to MCPServer

MCPServer has individual conditions (ImageValidated, GroupRefValidated,
PodTemplateValid, etc.) but no top-level Ready condition that summarizes
overall readiness. This is a standard Kubernetes pattern already used by
VirtualMCPServer and MCPRemoteProxy.

Add a Ready condition that reflects deployment readiness: True when
phase is Running, False for all other phases (Pending, Failed, Stopped,
Terminating). The condition is set in every status update path to
prevent staleness. Update the kubectl print column to show the condition
status instead of raw replica count, and add a separate Replicas column.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* Remove Ready condition unit tests in favor of integration tests

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Coverage Stats

17 of 31 new or added lines in 1 file covered. (54.84%)

8 existing lines in 2 files now uncovered.

53385 of 81510 relevant lines covered (65.5%)

64.72 hits per line