Repository navigation
MIR-1619: Choose cluster routes when connecting #1424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
evanphx
merged 5 commits into
main
from
evan/mir-1619-decide-how-to-route-to-a-cluster-per-connection-not-at
Nov 5, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b792f9a
Select direct or cloud cluster routing per connection
evanphx b58ecbb
Preserve TLS verification during cluster route discovery
evanphx 84ddff1
Merge branch 'main' into evan/mir-1619-decide-how-to-route-to-a-clust…
evanphx cf26a97
Reuse successful cluster routes and preserve fallback diagnostics
evanphx 63c6033
Resolve cluster credentials before selecting a route
evanphx File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This branch gives automatic entries the "direct when reachable, otherwise via cloud" label in the table. The JSON for the same entry (line 93, under the struct comment at lines 51-53) still reports
via_cloud: falsewith an emptyaddress, and that comment saysViaCloudis the reason an entry has no address. So a script readingcluster list --format jsoncan't tell an automatic entry from a broken one. It's the same ambiguity you fixed incluster add --format jsonwith thevia_cloud/force_cloudsplit.The fix could mirror that split. Either report the saved override as
force_cloud, or keepvia_cloudand document it as forced-only. Then add a field or route value for automatic entries, using the condition this branch already uses (Hostname == "" && XID != "" && Identity != ""), and update the comment to match. (I've attached this note here because line 53 isn't part of the diff.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is unchanged at
63c6033. The PR description now lists it as out of scope for the routing and diagnostics work, so I'm treating it as your accepted tradeoff and not a blocker. It's still a real gap for scripts that readcluster list --format json, so I'll leave the thread open for you or a reviewer to close, or to track as a follow-up.