You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: