-
Notifications
You must be signed in to change notification settings - Fork 2k
feat: add NetworkPolicy template #8052
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
✅ All required contributors have signed the F5 CLA for this PR. Thank you! |
|
I have hereby read the F5 CLA and agree to its terms |
|
Hi @GabboPenna, Thanks for this PR, Can you please create an issue for this so we can track it appropriately. |
Hi @AlexFenlon, i open a new issue: #8060 |
|
hi @GabboPenna, can you please also update:
|
|
This PR is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
Proposed changes
This PR adds optional NetworkPolicy support to the nginx-ingress Helm chart. It introduces:
networkPolicysection invalues.yaml:enabled)policyTypes(Ingress/Egress)podSelector,ingressandegressrule definitionscharts/nginx-ingress/templates/controller-networkpolicy.yamlthat renders a KubernetesNetworkPolicyresource whennetworkPolicy.enabled = trueWith 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 .)mainmainbranch and pulling from my fork’s branch