feat: make the compute networking integration optional#121
Merged
scotwells merged 1 commit intoMay 29, 2026
Merged
Conversation
…e cells Introduces a --feature-gates=NetworkingIntegration=false flag so operators can run compute on cells where network-services-operator (VPC) is not yet available. When disabled: no NetworkBinding is created, the Network scheduling gate is omitted from new Instances (and removed from existing ones), and the networking step is treated as immediately ready so Instances reach the runtime. Default is true, leaving all production behavior unchanged. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
scotwells
force-pushed
the
feat/networking-feature-flag
branch
from
5c2317e to
5024b97
Compare
scotwells
changed the title
scotwells
merged commit 70579e3
into
feat/federated-deployment-scheduling
8 checks passed
Merged
5 tasks
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
1 participant
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.
Summary
Compute's networking integration creates a network binding per Instance and holds each Instance behind a
Networkscheduling gate until networking is ready. On edge cells that don't yet have VPC available, that gate can never clear, so Instances are stuck and never run. This makes the networking integration optional: when turned off, Instances skip network binding and proceed straight to the runtime.Why it matters
It lets us bring compute up on cells before VPC is functional — workloads can be scheduled and run on a cell today, with networking added once VPC lands. Default behavior is unchanged (networking stays on); turning it off is an explicit opt-out for cells without VPC.
How to use it
Networking is enabled by default. To run compute on a cell that lacks VPC, disable the networking integration for that cell's operator; it will then neither create network bindings nor gate Instances on networking. Quota gating is unaffected.
Test plan
Networkgate and network bindings are created (unchanged behavior).Networkgate; Instances proceed to the runtime; the quota gate still applies.