Skip to content
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

[helm] Parameterize the DNS egress NetworkPolicy #15344

Open
lindhe opened this issue Dec 10, 2024 · 0 comments
Open

[helm] Parameterize the DNS egress NetworkPolicy #15344

lindhe opened this issue Dec 10, 2024 · 0 comments
Labels
area/helm type/feature Something new we should do

Comments

@lindhe
Copy link
Contributor

lindhe commented Dec 10, 2024

Is your feature request related to a problem? Please describe.

The DNS egress NetwrokPolicy is using a hard-coded port name, dns:

This is incompatible with some environments, for example the coredns installation used by RKE2 by default (it has port names udp-53 and tcp-53).

Describe the solution you'd like

I suggest we make this configurable via Helm values.

Describe alternatives you've considered

As a work-around, I'll be using Kustomize to edit the NetworkPolicy object. Another alternative would be to create a new NetworkPolicy manually.

Additional context

Additionally, the NetworkPolicy also has a hard-coded namespaceSelector:

I suggest we make that configurable as well, for similar reasons (and also for the security minded folks that want to restrict network policies even further).

I'm happy to help implement this!

@lindhe lindhe changed the title Parameterize the DNS egress NetworkPolicy [helm] Parameterize the DNS egress NetworkPolicy Dec 10, 2024
@JStickler JStickler added type/feature Something new we should do area/helm labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm type/feature Something new we should do
Projects
None yet
Development

No branches or pull requests

2 participants