Skip to content

feat: Report private service readiness from each node - #804

Merged
scotwells merged 1 commit into
feat/psc-vpc-accessfrom
feat/psc-node-readiness
Oct 8, 2026
Merged

scotwells merged 1 commit into
feat/psc-vpc-accessfrom
feat/psc-node-readiness

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Summary

A valid access policy does not prove that every node has installed its forwarding path. Report current programming readiness from consumer and producer nodes, tied to the policy lifetime and network configuration. Reports expire and are withdrawn when programming becomes invalid or a node restarts.

This lets integrating services wait for the complete network path before exposing private access.

Depends on #803.

Test plan

  • Linux controller and route-planner race tests; targeted lint.
  • Remote path reports, configuration changes, unhealthy attachments, stale policy writes, and feature disablement.
  • 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:20
@scotwells
scotwells requested a review from a team as a code owner October 8, 2026 19:20
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-node-readiness 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