ai-assisted=yes Add documentation for replaceChainRules enforcement cycle#357
Merged
geofffranks merged 1 commit intodevelopfrom Apr 7, 2026
Merged
Conversation
ameowlia
requested changes
Apr 2, 2026
Member
ameowlia
left a comment
There was a problem hiding this comment.
If you want to be extra, it would be nice to have examples that show the section of iptables rules between each step in a happy path case.
Documents the vxlan-policy-agent enforcement cycle, including the decision tree for replaceChainRules, naming conventions, state evaluation and recovery, and safety explanations. Made-with: Cursor
bc36b6c to
7c6318e
Compare
ameowlia
approved these changes
Apr 7, 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.
Made-with: Cursor
Summary
Documents the vxlan-policy-agent enforcement cycle, including the decision tree for replaceChainRules, naming conventions, state evaluation and recovery, and safety explanations.
Backward Compatibility
Breaking Change? no