Repository navigation
Report whether a location's address range is in place on the cell - #32
Merged
Merged
Conversation
The networking operator leaves a Subnet's Programmed condition for the data plane to close, and nothing on a Datum cell ever closed it, so every address range reads as not programmed in the project while its workloads serve traffic. The answer is here: the VPC built for the network's presence carries the subnet's range, and is ready once the fabric identity lands. A new reconciler writes Programmed on the propagated Subnet copy from that VPC: in place once a ready VPC carries the range, in progress while the VPC is being built or awaits its identity, and not programmed for a range the VPC was built without, since its address space is fixed at creation. The report is made against the project's generation stamped on the copy, and the federation carries it back. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Collaborator
Author
|
Related: project-side reader datum-cloud/network-services-operator#640, hub aggregation https://github.com/datum-cloud/infra/pull/6988. All three are independently safe to ship; the signal is live once all three are deployed. |
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
privateip
approved these changes
Oct 14, 2026
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
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.
Why
Every subnet in a project reads
NotProgrammedforever, anddatumctlnames it as the root cause on every network, while the workloads behind it serve traffic. The networking operator leaves the Subnet'sProgrammedcondition for the data plane to close, the way it does for NetworkInterfaces, and nothing on a cell ever closed it.What changes for a customer
Once the companion PRs land, a network's address range in a location reads Ready only when the cells there actually route it. A range a VPC was built without surfaces as
NotProgrammedinstead of silently never working.How
The vpc-controller already builds a VPC per network presence carrying the subnet's range, and marks it ready once the fabric identity lands. A new
SubnetReconcilerturns that into the report:ProgrammedTrue/ProgrammedFalse/ProgrammingInProgressFalse/NotProgrammedThe condition's
observedGenerationis the project's generation stamped on the copy by the operator, falling back to the copy's own, so the project can match the report to what it asked for. It writes only the one condition on the propagated copy; the federation carries it back to the project.RBAC gains
subnets/statusupdate.Verified
Unit tests for each row above and for the generation fallback. Lint and vet clean.
Rollout
Safe on its own: until the hub aggregates and the operator reads it, the report stays on the cell copy.
Related PRs linked in the first comment.
🤖 Generated with Claude Code