fix: make health probes configurable with better defaults#202
Merged
vishnu-narayanan merged 4 commits intomainfrom Apr 2, 2026
Merged
fix: make health probes configurable with better defaults#202vishnu-narayanan merged 4 commits intomainfrom
vishnu-narayanan merged 4 commits intomainfrom
Conversation
nslookup in BusyBox v1.37+ (shipped in the chatwoot image) exits 1 when intermediate search domain lookups return NXDOMAIN, even if the final lookup succeeds. This causes the init-redis until loop to hang indefinitely on clusters with ndots:5 (the Kubernetes default). getent hosts uses the system C library resolver which returns the first successful result and exits 0, matching the expected behavior. Fixes #200
- Add timeoutSeconds: 5 to liveness, readiness, and startup probes (was defaulting to 1s) - Increase startup probe failureThreshold from 30 to 60 (~10 min budget) - Move probe configuration to values.yaml so customers can tune without forking
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.
Summary
timeoutSeconds: 5to liveness, readiness, and startup probes (was defaulting to K8s implicit 1s)failureThresholdfrom 30 to 60 (~10 min budget instead of ~5.5 min)values.yamlso self-hosted customers can tune without forking the chartContext
Self-hosted customer reported pods stuck in restart loops due to health check failures. Root cause was CPU-starved pods taking too long to boot Rails, combined with the implicit 1s
timeoutSecondskilling pods that were slow to respond after startup.Test plan
helm templaterenders probes correctly with default values