Health Check#54
Merged
Merged
Conversation
Step7750
approved these changes
Mar 12, 2026
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
2 participants
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.
Refs CSF-775
Note
Medium Risk
Introduces a new liveness probe that can trigger container restarts if the new
/api/v1/healthroute is miswired or unavailable. Code changes are small, but the deployment behavior change can impact uptime if configured incorrectly.Overview
Adds a new
api/v1/healthrouter that returns200 OKwith bodyOK, and mounts it at/healthunder the v1 API.Updates the Knative/Cloud Run service manifest to include an HTTP
livenessProbehitting/api/v1/healthon port80, enabling automated restarts when the service becomes unhealthy.Written by Cursor Bugbot for commit e0210a9. This will update automatically on new commits. Configure here.