stacklok / toolhive / 21428413335

60%

Build Type

push

github

Committed by web-flow

Commit Message

Integrate status reporting into vMCP runtime (#3457)

* Integrate status reporting into vMCP runtime

Wire up periodic status reporting to enable vMCP runtime to report
operational status to the control plane (Kubernetes API or CLI logging).

Changes:
  - Add BuildStatus() method to health.Monitor that converts health state
    to vmcp.Status format with phase determination, backend details, and
    Kubernetes-style conditions
  - Create periodicStatusReporting() in server package that runs in
    background goroutine, pulling health data every 30 seconds and
    sending to configured reporter
  - Integrate status reporting lifecycle into server.Start() and Stop()
    with proper shutdown handling
  - Update commands.go to use factory pattern (vmcpstatus.NewReporter)
    instead of hardcoded LoggingReporter, enabling auto-detection of
    K8s vs CLI mode via environment variables
  - Add comprehensive tests for status building logic (phase determination,
    condition generation, message formatting)

Phase determination logic:
  - Ready: All backends healthy (or no backends yet - cold start)
  - Degraded: Some backends healthy, some degraded/unhealthy
  - Failed: No healthy backends
  - Pending: Waiting for backends to be discovered

The implementation respects the separation between health monitoring
(data gathering) and status reporting (persistence), with K8sReporter
handling Kubernetes-specific fields like ObservedGeneration.

Related-to: #3149

* fixes from review

---------

Co-authored-by: taskbot <taskbot@users.noreply.github.com>

Run Details

231 of 265 new or added lines in 8 files covered. (87.17%)

3 existing lines in 2 files now uncovered.

38677 of 64086 relevant lines covered (60.35%)

77.05 hits per line