Skip to content

feat: Restrict private service access to authorized VPCs - #803

Merged
scotwells merged 1 commit into
feat/psc-frontend-dataplanefrom
feat/psc-vpc-access
Oct 8, 2026
Merged

scotwells merged 1 commit into
feat/psc-frontend-dataplanefrom
feat/psc-vpc-access

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Summary

VPCs must reach shared private services only while access is authorized. Bind translated service access to the current consumer VPC lifetime, reject conflicting frontend claims, and withdraw forwarding when authorization or network eligibility changes.

Frontend translation remains disabled by default. Existing direct-service grant identifiers remain compatible during router upgrades.

Depends on #802 and network API #30.

Test plan

  • Linux race tests for controllers, route planning, router configuration, and command wiring; targeted lint.
  • VPC identity mismatch, authorization bounds, both conflict orders, recovery, and default-off configuration.
  • Full task ci: macOS compiler crash; complete stack qualification pending.

Related to datum-cloud/enhancements#921 and #798.

@scotwells
scotwells marked this pull request as ready for review October 8, 2026 19:14
@scotwells
scotwells requested a review from a team as a code owner October 8, 2026 19:14
privateip
privateip previously approved these changes Oct 8, 2026
@scotwells
scotwells added this pull request to stack #807 October 8, 2026 19:21
@scotwells
scotwells merged commit 9694e48 into main Oct 8, 2026
15 checks passed
@scotwells
scotwells deleted the feat/psc-vpc-access branch October 8, 2026 20:15
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.

2 participants