Carry edge policy from the control plane out to the edges#227
Draft
scotwells wants to merge 1 commit into
Draft
Conversation
Describes how firewall and connector policy authored centrally is delivered to each edge, and how each edge reads it on arrival. Named for what it does rather than the tool that moves it, so the intent stays legible if the mechanism changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JbCy8vy66RdNYzGSgqH6P6
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.
What this delivers
The protections customers configure — firewall and connector rules — are authored in one place, the control plane. For them to take effect, they have to reach every edge. This describes how that delivery happens: which policies travel out to the edges, and how each edge should read them once they arrive.
Why it's framed around responsibility
The configuration here is named for what it does — carrying policy from the center out to the edges — rather than the specific tool that moves it. That keeps the intent readable on its own terms, even if the mechanism underneath it changes later.
Scope
Delivery wiring for the test environment. It mirrors how policy reaches the edge in production so tests see the same propagation behavior customers depend on.