Skip to content

feat: Define private DNS access and publication APIs - #231

Draft
scotwells wants to merge 19 commits into
feat/private-dns-zone-isolationfrom
feat/internal-dns-project-api
Draft

scotwells wants to merge 19 commits into
feat/private-dns-zone-isolationfrom
feat/internal-dns-project-api

Conversation

@scotwells

@scotwells scotwells commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Configure private names through isolated contexts, zones, and registrations. Product services submit addresses and eligibility together, while DNS reports publication readiness. Regional access requests identify the context and destination without caller-managed DNS versions. Project RBAC controls writes, and schemas validate the resource contracts.

User experience

Network services requests a managed private namespace through DNSResolverContext. Users associate additional private zones through DNSZoneAssociation and configure aliases through DNSNamingPolicy. Product services reserve names through DNSRegistration and submit records and eligibility in DNSRecordContribution.spec. Network services requests access with a context, region, and destination address.

Test plan

  • CI: API and controller tests
  • CI: Lint and generated manifests
  • CI: Container packaging
  • CI: Repository end-to-end tests

Stacked on #230. Architecture: #229.

@scotwells
scotwells force-pushed the feat/internal-dns-project-api branch from 987a1ba to 0e872bb Compare October 9, 2026 01:33
@scotwells
scotwells added this pull request to stack #240 October 9, 2026 02:17
@scotwells
scotwells force-pushed the feat/internal-dns-project-api branch from 5e6d0c2 to d999c3a Compare October 12, 2026 17:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant