Repository navigation
Conversation
Describe automatic private names and inherited resolver settings for VPC resources. Define ownership across project, federation, and edge APIs. Key changes: - Define regional access and trusted network identity. - Show commented API examples and rollout criteria.
Describe the VPC DNS integration as network services so the proposal uses product terminology. Key changes: - Align prose, diagrams, and YAML explanations.
Use the DNSRecordContribution kind when describing product publication. Key changes: - Match the publication contract in the DNS API.
Keep the proposal on the current network services baseline.
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.
Summary
VPC workloads resolve private resource names through inherited resolver settings. This proposal defines how network services provide VPC DNS access while product services publish their records. Network services submits the DNS context, region, and private destination and verifies the Galactic network path before delivering resolver settings. Architecture diagrams, commented API examples, and release criteria explain the consumer experience and integration boundaries.
Test plan
Related to datum-cloud/enhancements#921.