fix(functions): reload kong after edge runtime restart#4990
Open
okedeji wants to merge 1 commit intosupabase:developfrom
Open
fix(functions): reload kong after edge runtime restart#4990okedeji wants to merge 1 commit intosupabase:developfrom
okedeji wants to merge 1 commit intosupabase:developfrom
Conversation
okedeji
force-pushed
the
fix/kong-dns-stale-edge-runtime
branch
from
008b444 to
ebc3bd7
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.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
After
supabase functions serverestarts the Edge Runtime container (on file change or initial serve), Kong's DNS cache still points to the old container IP, causing 502 errors on/functions/v1/*endpoints.closes #4757
What is the new behavior?
Runs
kong reloadafter each Edge Runtime restart to flush DNS cache and resolve the new container IP.Additional context
The reload is non-disruptive. Kong flushes DNS without dropping in-flight connections. If the reload fails, a warning is printed to stderr and execution continues.