fix: default readiness probe to /healthz/readiness#149
Merged
krider2010 merged 2 commits intoJun 15, 2026
Conversation
The /healthz/readiness endpoint performs a deeper check (verifies DB and queue connectivity) making it more accurate as a readiness signal. /healthz only checks that the process is alive, which is better suited for the liveness probe. The path remains configurable via probes.readiness.path so operators can revert to /healthz if preferred.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
krider2010
approved these changes
Jun 15, 2026
krider2010
added a commit
that referenced
this pull request
Jun 15, 2026
Add context under the #149 entry: pods now wait for DB connectivity and migrations before becoming Ready, and how to revert via probes.readiness.path. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Description
Changes the default
probes.readiness.pathinvalues.yamlfrom/healthzto
/healthz/readiness.Why
/healthzonly checks that the n8n process is running (process-alive check)/healthz/readinesschecks that n8n is actually ready to serve traffic —it verifies DB connectivity and (in queue mode) Redis connectivity
/healthzfor readiness means pods are marked ready before they canactually handle requests, causing errors during startup/rolling updates
Backwards compatibility
The path is fully configurable. Users who prefer the old behaviour can set:
Type of Change
Changes Made
Just the value of the readiness path at the values.yaml to check the DB at the readiness checks.