Skip to content

feat: Define private service access and node readiness - #30

Merged
privateip merged 1 commit into
mainfrom
feat/psc-service-frontends
Oct 8, 2026
Merged

privateip merged 1 commit into
mainfrom
feat/psc-service-frontends

Conversation

@scotwells

@scotwells scotwells commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Private services need to bind access to a specific VPC and stop forwarding when authorization expires. Extend service policies with a consumer address, VPC lifetime reference, authorization deadline, and current node programming reports.

This is the shared API prerequisite for Galactic Private Service Connect; it adds no DNS-specific behavior.

Test plan

  • Linux API unit tests with race detection; real API admission and stale status-write checks.
  • Generated CRDs, deepcopy methods, API reference, and lint.
  • GitHub build, lint, unit, and cluster E2E checks.

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

@scotwells
scotwells marked this pull request as ready for review October 8, 2026 19:04
@scotwells
scotwells requested a review from a team as a code owner October 8, 2026 19:04
@privateip
privateip merged commit fc3154b into main Oct 8, 2026
6 checks passed
@privateip
privateip deleted the feat/psc-service-frontends branch October 8, 2026 20:40
privateip added a commit to datum-cloud/galactic that referenced this pull request Oct 8, 2026
main pinned go.datum.net/network to the head of datum-cloud/network#30, which predated #29, and this branch pinned #29's merge. Both are now on network main, so go.mod pins fc3154b, the #30 merge, which carries the private service types main uses and the NetworkRule selector this branch uses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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