Read gateway domain from observed XLS, not connection details#1240
Merged
Conversation
4 tasks
mdnix
force-pushed
the
appcat/717/fix/gatewaydomain-obs
branch
from
e952e4e to
0540030
Compare
mdnix
approved these changes
Jul 13, 2026
…ab3167ba033264b5b83d1564dd
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.
Summary
Reading the gateway domain from published connection details is racy: if the first publish beats port allocation, the domain never arrives and the cert-SAN readiness gate stays closed, stranding the instance at READY=False. Read it from the observed XListenerSet instead. Fixes MariaDB, Redis, and CNPG
Checklist
/mergecomment.Link: vshn/appcat#717