Repository navigation
Conversation
mattdjenkinson
previously approved these changes
Oct 12, 2026
This was referenced Oct 12, 2026
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
Propose a Datum Network Load Balancer API with separate listeners, routes, and
NetworkServicebackends. Each selected location gets an IP per requested family and a stable generated hostname for customer CNAMEs. Locations follow backend service placement by default. A future Global Services Load Balancer will handle global entry points. The proposal covers TCP and UDP, health checks, TLS, and a Gateway API L4 compatibility target.The IPv4 data-plane plan uses a stateful TCP and UDP proxy for IPv4 clients reaching IPv6 services. IPv4 address requests remain outside the first API release.
Review focus