Repository navigation
feat: Tell serving locations what each load balancer needs - #628
Merged
Merged
Conversation
scotwells
changed the title
scotwells
marked this pull request as ready for review
October 23, 2026 14:55
kevwilliams
reviewed
Oct 23, 2026
kevwilliams
left a comment
kevwilliams
left a comment
Contributor
There was a problem hiding this comment.
Diff exceeds auto-review threshold (1642 lines). Flagging for human review.
Each location checks its load balancer backends with TCP, HTTP or HTTPS probes, and only backends with a recent successful check are eligible for traffic, so a failed backend stops receiving new connections on its own. Key changes: - Add a cell-local backend health record and probe runner - Fail closed when a probe fails, is missing or goes stale - Require a matching attachment UID before probing a backend - Report that probing is unavailable until a location can reach VPC backends
Each location that will serve a load balancer now receives what it needs to serve: the address, port, backends and health check settings. Locations validate this request but do not program traffic yet. Key changes: - Publish scoped cell intent per listener and per-location IPv6 address - Hold back setups the data plane cannot serve yet, such as several addresses on one listener or more than 64 backends - Withdraw old intent when a route is removed or an address changes
scotwells
force-pushed
the
codex/nlb-cell-intent
branch
from
October 23, 2026 15:40
af391f7 to
f801336
Compare
scotwells
force-pushed
the
codex/nlb-source-identity
branch
from
October 23, 2026 15:40
8bafdab to
8162a4b
Compare
Base automatically changed from
codex/nlb-source-identity
to
codex/nlb-api-foundation
October 23, 2026 15:40
|
|
2 tasks done
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
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.
Closed by mistake while restacking; continued in #716.
Related to #611 and datum-cloud/enhancements#884