Repository navigation
docs(networking): propose Private Service Connect - #798
Merged
Merged
Conversation
scotwells
changed the title
scotwells
marked this pull request as ready for review
October 8, 2026 17:00
privateip
approved these changes
Oct 8, 2026
This was referenced Oct 8, 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.
Private Service Connect gives workloads private access to shared services without connecting entire VPCs. Propose the capability using the enhancement template, with user stories, architecture diagrams, readiness requirements, and release considerations.
Design Details defines the complete ServiceEndpoint and ServiceRoutePolicy design: why publication and authorization are separate, resource relationships and ownership, namespaces and references, replica selection, reconciliation, status, and lifecycle. Explain the complete API through YAML manifests with comments above the fields, including the proposed consumerVPCRef and frontend extensions. Identify compatibility requirements and outstanding conflict, readiness, and revocation contracts.
Link the routing reference and Internal DNS proposals in datum-cloud/enhancements#922 and datum-cloud/dns-operator#229.
Validation: template sections, front matter, TOC, relative links, code fences, YAML examples and whitespace checks passed. The new resource relationship diagram rendered and was visually checked; the other three diagrams are unchanged from their verified versions. Local task ci remains blocked by a Clang 23.1.1 crash during eBPF generation, before lint, build, or tests ran.