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
LCORE-1859: Enhance /readiness endpoint with degraded mode reporting
#1781 introduced
"degraded mode support" - the ability to start lightspeed-stack and keep it running
even when llama-stack server might not be available.
This PR adds comprehensive degraded mode status reporting to the /readiness endpoint
while maintaining clean API boundaries and Kubernetes probe semantics.
- Enhanced HealthStatus enum with DEGRADED and UNHEALTHY service-level statuses
while preserving provider-level statuses (OK, ERROR, NOT_IMPLEMENTED, UNKNOWN)
- Enhanced /readiness endpoint to return 200 (ready=true) in degraded mode
following Kubernetes semantics; only returns 503 when truly unhealthy
- Refactored to avoid leaking implementation details in API responses:
* Removed llama_stack field from ReadinessResponse
* Removed Llama Stack version tracking from DegradedModeTracker
* Focus on functional impacts rather than internal technology stack
This design keeps internal implementation details (Llama Stack) private while
exposing clear functional impacts to API consumers.
Signed-off-by: Anik Bhattacharjee <anbhatta@redhat.com>
0 commit comments