Skip to content

fix(coglet): return 503 from /health-check when not ready#2732

Open
bfirsh wants to merge 2 commits intomainfrom
fix/health-check-503
Open

fix(coglet): return 503 from /health-check when not ready#2732
bfirsh wants to merge 2 commits intomainfrom
fix/health-check-503

Conversation

@bfirsh
Copy link
Member

@bfirsh bfirsh commented Feb 16, 2026

Summary

  • /health-check now returns 200 only when status is READY; all other statuses (STARTING, BUSY, SETUP_FAILED, DEFUNCT, UNHEALTHY) return 503
  • This lets load balancers and Kubernetes probes work without parsing the response body
  • Updated docs and tests to match

Builds on #2731.

Test plan

  • cargo test -p coglet -- health_check — 4 tests pass
  • mise run docs:llm:check passes

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@bfirsh bfirsh requested a review from a team as a code owner February 16, 2026 22:50
@bfirsh bfirsh force-pushed the fix/health-check-503 branch from f2667b6 to 548f853 Compare February 16, 2026 23:01
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@bfirsh bfirsh force-pushed the fix/health-check-503 branch from 548f853 to de50eaf Compare February 16, 2026 23:33
Copy link
Member

@tempusfrangit tempusfrangit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note this is a behavioral departure from the original cog http server. In the coglet implementation we avoided making this change until we were ready to make breaking changes.

More importantly, is 503 correct while we're in a BUSY state? This is going to matierially change our contract. Likely we want to BUSY to be 429 if anything?

@bfirsh before we land this one we should make sure we want BUSY to be 503. Even as a 429, it is likely we will need to change director and other ecosystem tools.

Base automatically changed from docs/health-check-endpoint to main February 17, 2026 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments