Repository navigation
fix: Show why a route leaves a network load balancer unserved - #755
Merged
Merged
Conversation
When no route served an address, the load balancer's Programmed and Ready conditions said NotServed with "No route serves this address", even when a route was attached and had been rejected for a reason it already reported, such as a backend socket another NLB owns. Users had to find and read the route to learn why. Key changes: - Carry the reason and message of a rejected route onto the address and the load balancer's Programmed and Ready conditions - Read only conditions the route sets itself, never ones that follow the load balancer's status - Reconcile a load balancer when one of its routes changes
kevwilliams
approved these changes
Oct 27, 2026
kevwilliams
left a comment
kevwilliams
left a comment
Contributor
There was a problem hiding this comment.
Verified the rejection is copied only from current-generation conditions on routes whose parent is this load balancer and listener, and a route update re-queues each load balancer it names.
privateip
approved these changes
Oct 27, 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
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
A network load balancer whose route was rejected said only "No route serves this address", even though the route already knew why.
Users had to find the route to learn that, for example, another load balancer already owns its backend.
The load balancer's status now carries the route's reason and message, so the cause shows on the load balancer itself.
Test plan
Related to #722
Related to datum-cloud/galactic#1138
Related to #718