Add optional default-deny NetworkPolicy template.#18
Merged
mbaldessari merged 1 commit intovalidatedpatterns:mainfrom Apr 30, 2026
Merged
Conversation
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.
Add optional default-deny NetworkPolicy template
Add a namespace-wide default-deny NetworkPolicy that blocks all ingress
and egress for pods without an explicit allow policy. Gated by
defaultDenyNetworkPolicy.enabled (default false) so existing patterns
are unaffected.
Patterns that need zero-trust network isolation can enable this and
provide per-pod allow rules via vault.server.networkPolicy (already
supported by the upstream vault subchart).
Tested on an OpenShift 4.21 cluster with the layered-zero-trust pattern.