CE: Return 503 health when DB down + graceful session errors#299
Merged
CE: Return 503 health when DB down + graceful session errors#299
Conversation
added 2 commits
April 15, 2026 21:22
- Health endpoint returns HTTP 503 with status 'degraded' when database is unreachable, so k8s readiness probe correctly fails - Session guard middleware returns styled 503 page for session-dependent routes when SessionManagerLayer is not available, replacing raw tower-sessions error text - Updated integration tests to match new behavior
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two fixes for DB-unavailable scenarios:
/healthreturns 503 (not 200) whendb_connectedis false, so k8s readiness probe fails correctlyHow
StatusCode::SERVICE_UNAVAILABLEwith{"status":"degraded",...}when DB ping failssession_guardmiddleware checks forSessionin request extensions before session-dependent routes; returns a styled HTML 503 page when missing/,/health,/robots.txt,/sitemap.xml,/favicon.ico,/checkout/cancel,/webhook/*) pass through unaffectedWhy
When the cloud Postgres is unreachable, the pod still passes k8s readiness checks and routes traffic. Users see raw error strings on pricing/signup/login/dashboard pages.
Test plan