fix: read a location's subnet range from spec when status is absent - #8
Merged
Conversation
A location's Subnet arrives by Karmada propagation, which carries spec and never the status subresource, and no cell runs the reconciler that would populate status there. networksForContext read status only, so it found no address space, never created the VPC, and every interface stayed at Prepared=False/AwaitingVPC. Confirmed on us-central-1-staging-lab: the propagated copy carries startAddress fd20:: and prefixLength 64 in spec, with an empty status. Status still wins where it exists, which is the control plane's own copy. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
privateip
approved these changes
Aug 21, 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
2 participants
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.
Instances cannot get VPC networking even now that a location has address space. The subnet reaches the cell, but the VPC is never created and every interface sits at
Prepared=False / AwaitingVPC.networksForContextreadssubnet.Status.StartAddressandStatus.PrefixLength. A location's copy arrives by Karmada propagation, which carries spec and never the status subresource, and no cell runs the reconciler that would populate status there. So the controller sees a subnet with no range and concludes the location has no address space.Live on
us-central-1-staging-lab— the propagated copy:Read status first and fall back to spec, which is what network-services-operator's own
subnetGatewaydoes with the same object for the same reason. Status still wins where it exists, which is the control plane's own copy.Related
Completes the chain behind datum-cloud/compute#244, which waits on
Prepared. The subnet itself arrives via datum-cloud/network-services-operator#396 and #397.Not fixed here, and worth its own change:
vpc.Spec.Networksis written only at creation andVPCSpecis immutable, so a second address family arriving later is silently dropped.