Probe Postgres readiness over TCP so the pod isn't ready before 5432 is open - #130
Merged
Conversation
thomasjm
force-pushed
the
postgres-readiness-tcp
branch
from
August 26, 2026 02:06
3f4d8db to
22a6b77
Compare
thomasjm
force-pushed
the
postgres-readiness-tcp
branch
from
August 26, 2026 02:48
22a6b77 to
a6a0767
Compare
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.
The readinessProbe ran
pg_isready -U <user>with no-h, so it probes the Unix socket. Duringinitdba temporary socket-only server answers that, so the pod can report ready while TCP 5432 is still closed — a caller that port-forwards and connects as soon as the pod is Ready gets connection refused.-h 127.0.0.1makes the probe check what callers actually connect to.Untested locally:
stack buildhere wanted to reinstall GHC 9.12.4 and failed.