Repository navigation
Add scalable platform service route policies - #27
Merged
Merged
Conversation
scotwells
force-pushed
the
feat/service-route-policy-api
branch
from
October 6, 2026 16:35
b037f63 to
bf0955a
Compare
privateip
approved these changes
Oct 7, 2026
scotwells
marked this pull request as ready for review
October 7, 2026 20:00
This was referenced Oct 7, 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
Add the control-plane API for attachment-scoped platform services.
Scope
ServiceEndpointandServiceRoutePolicyAPI types.VPCAttachmentservice replicas by explicit reference or label selector.NodeLocalandPreferNodeLocal: the latter chooses a ready same-node replica first and falls back to a remote replica while preserving the consumer source address.Acceptedcondition withobservedGeneration.Galactic PR #634 consumes this API and programs attachment-scoped TC-eBPF state without exposing service routes in consumer instances.
Validation