feat: add NetworkPolicy template #8052
Open
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.
Proposed changes
This PR adds optional NetworkPolicy support to the nginx-ingress Helm chart. It introduces:
networkPolicy
section invalues.yaml
:enabled
)policyTypes
(Ingress/Egress)podSelector
,ingress
andegress
rule definitionscharts/nginx-ingress/templates/controller-networkpolicy.yaml
that renders a KubernetesNetworkPolicy
resource whennetworkPolicy.enabled = true
With this change, chart consumers can declare fine‑grained network controls for their Ingress controller pods without external manifests.
Checklist
Before creating a PR, run through this checklist and mark each as complete.
helm lint .
)main
main
branch and pulling from my fork’s branch