FWIW: The Helm chart has network policy in place: https://github.com/argoproj/argo-helm/blob/main/charts/argo-cd/templates/redis/networkpolicy.yaml https://git

FWIW: The Helm chart has network policy in place: https://github.com/argoproj/argo-helm/blob/main/charts/argo-cd/templates/redis/networkpolicy.yaml https://github.com/argoproj/argo-helm/blob/main/charts/argo-... If you're using a CNI that supports network policy (e.g. AWS VPC CNI on EKS, Calico, etc.), I think this should more or less cover you, but I haven't personally tested it. I think it's also probably a better practice to install "control plane" type software like Argo on a different, dedicated cluster. Argo supports this concept (and can in fact manage deployments in multiple clusters remotely). This way your main mission workloads are completely segmented from your privileged control plane software. Just as another defense-in-depth measure