Derive Gateway addresses from Service status instead of hardcoded 127.0.0.1#36
Merged
RobbieMcKinstry merged 1 commit intotrunkfrom Apr 1, 2026
Merged
Derive Gateway addresses from Service status instead of hardcoded 127.0.0.1#36RobbieMcKinstry merged 1 commit intotrunkfrom
RobbieMcKinstry merged 1 commit intotrunkfrom
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
….0.0.1 Replace the hardcoded 127.0.0.1 Gateway address with dynamic address derivation from cluster state. The address resolution follows this priority order: 1. Static addresses from gateway.spec.addresses (user-specified) 2. LoadBalancer ingress IPs/hostnames from the data plane Service 3. Node internal IP (for NodePort/hostPort, e.g. Kind clusters) 4. Service ClusterIP When no address is available (e.g. first reconciliation before the Service exists), the Gateway is set to Accepted=True but Programmed=False with reason AddressNotAssigned. This is required for the GatewayWithAttachedRoutes conformance test, which expects real addresses from the Service status rather than localhost.
RobbieMcKinstry
force-pushed
the
robbie/multi-1094
branch
from
379f7f3 to
0c3f398
Compare
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.
Replace the hardcoded 127.0.0.1 Gateway address with dynamic address
derivation from cluster state. The address resolution follows this
priority order:
When no address is available (e.g. first reconciliation before the
Service exists), the Gateway is set to Accepted=True but
Programmed=False with reason AddressNotAssigned.
This is required for the GatewayWithAttachedRoutes conformance test,
which expects real addresses from the Service status rather than
localhost.