Make kubectl port-forward actually restart when it exits - #134
Merged
Merged
Conversation
thomasjm
force-pushed
the
fix-port-forward-restart
branch
from
September 1, 2026 09:22
8ddd1ce to
5a36a44
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 restarter loop passed the same log
HandletocreateProcesson every iteration, butcreateProcesscloses the handles it's given, so the second iteration threw and killed the thread — leaving the local port unbound for the rest of the run. Also gates the Postgres readiness probe on the pod IP, sincepg_isready -h 127.0.0.1reports ready against the temporary server the bitnami entrypoint runs during setup, minutes before the real one starts.