docs: single shared Gateway listener for all coordinators - #1740
Open
as51340 wants to merge 1 commit into
Open
Conversation
Coordinators are no longer exposed through one Gateway listener/TCPRoute each: they share a single listener on ports.boltPort with one TCPRoute fanning out to every coordinator Service, so the Gateway round-robins connections across them. Drops externalAccessConfig.gateway.coordinatorPortBase and documents the dataPortBase vs ports.boltPort collision rule.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
as51340
added
the
feature
as51340
changed the title
8 tasks
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.
Release note
Documented the HA Helm chart change where all coordinators are exposed through a single Gateway API listener and a single TCPRoute on
ports.boltPortinstead of one listener/TCPRoute per coordinator. The Gateway round-robins new connections across every coordinator Service, so clients need only one coordinator address and scaling the coordinator tier no longer adds a listener or a port.Changes in
pages/clustering/high-availability/setup-ha-cluster-k8s.mdx:externalAccessConfig.gateway.coordinatorPortBaseno longer exists (chart rendering fails if set), clients must move to<gateway-host>:<boltPort>, and existing Gateways must replace theircoordinator-{id}-boltlisteners with a singlecoordinators-boltlistener.<hostname>:<boltPort>is registered as every coordinator's routingbolt_server.dataPortBase + idvs.ports.boltPortcollision rule that fails rendering when both tiers go through the Gateway.coordinators-bolton 7687.externalAccessConfig.gateway.coordinatorPortBaserow from the configuration table and clarified thedataPortBaseandports.boltPortdescriptions.Related product PRs
PRs from product repo this doc page is related to:
Checklist:
bugfixorfeaturelabel, based on the product PR type you're documentingNote
The chart PR does not bump
Chart.yaml(still1.3.3, which is released and does shipcoordinatorPortBase), so the breaking-change callout is worded as "HA chart versions after 1.3.3". If a specific version is decided before the chart PR merges, that line should be updated.