Add NetworkPolicy for the ZTWIM namespace#145
Open
p-rog wants to merge 25 commits into
Open
Conversation
…s and default deny network policy
… later broken DNS
…t into network-policy
… and Keycloak port
…ft.io/ingress: triggers OVN-K's special ACL handling for host-network traffic
…snwers on both an internal hostname (for back-channel) and an external hostname (for browser redirects)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
Adds network isolation for the
zero-trust-workload-identity-managernamespace using the default-deny + per-pod allow pattern.Depends on ztwim-chart PR #5 which adds the NetworkPolicy templates to the wrapper chart. Until that PR merges, the values in this PR are silently ignored by Helm (no NetworkPolicies created).
Changes
overrides/values-ztwim-network-policy.yamlwith per-pod rules for spire-server, OIDC discovery provider, SPIFFE CSI driver, and ZTWIM operatorextraValueFilesinvalues-hub.yamlfor the ZTWIM applicationPer-pod rules
Not covered (by design): spire-agent uses
hostNetwork: true+hostPID: true— Kubernetes NetworkPolicies do not apply to hostNetwork pods.Test plan
oc apply🤖 Generated with Claude Code