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

Add egress NetworkPolicies #2807

Closed
dan-m8t opened this issue Jul 5, 2024 · 2 comments
Closed

Add egress NetworkPolicies #2807

dan-m8t opened this issue Jul 5, 2024 · 2 comments
Labels

Comments

@dan-m8t
Copy link

dan-m8t commented Jul 5, 2024

Is your feature request related to a problem?

By default we deploy default-deny ingress/egress rules into our namespaces. This means when I deploy Argo CD into a namespace with NetworkPolicies enabled it won't work because Argo CD is missing these egress rules. For example argocd-application-controller egress repo-server port to the argocd-repo-server. Only ingress rules are created.

Related helm chart

argo-cd

Describe the solution you'd like

A configurable helm value that allows the creation of egress rules when needed or wanted.

Describe alternatives you've considered

For now I disabled our default deny egress rule.

Additional context

No response

@dan-m8t dan-m8t added the enhancement New feature or request label Jul 5, 2024
@dan-m8t dan-m8t changed the title Add egress NetworPolicies Add egress NetworkPolicies Jul 5, 2024
@omerap12
Copy link

I can help with that :)

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants