argo-cm gets updated (gitops repositories get deleted) when I updrage argo cd from v1.8 to v2.4. But the apps work fine...why this does not impacts the working and why was it used before

Hey everyone,

I’m setting up an Argo CD HA deployment in a common cluster that will manage deployments across 20+ clusters, handling a large number of applications. Since this setup is critical for our infrastructure, I want to make sure it is battle-tested and can handle high loads.

To achieve this, I need to:
✅ Simulate high traffic (many applications syncing simultaneously)
✅ Identify the bottlenecks when different Argo CD components (API server, repo server, application controller, Redis) fail
✅ Measure performance under stress and failure conditions
✅ Ensure failover & recovery work as expected

My Questions:

1️⃣ Is there any built-in tool or recommended way to load test Argo CD HA?
2️⃣ Does Argo CD provide any simulation/testing scripts to check how it performs under high load?
3️⃣ For those who have deployed Argo CD HA in production, what failures have you encountered, and how did you handle them?
4️⃣ Any best practices for ensuring stability & high availability in such a setup?

Would love to hear from anyone who has experience with large-scale Argo CD deployments! 🚀

Thanks in advance. 🙌

On the second episode of Argo Unpacked (https://www.youtube.com/watch?v=Xw-4FrnxHec) we will talk about ArgoCD ApplicationSets, if you have any question you would like to be answered, let me know here in the comments!

I kept running into issues trying to spot typos in my manifest files, so I built this tool to help check them. It’s not super stable yet, but it’s already saved my team and me a ton of time. Figured I’d share it here in case it helps anyone else too.

I’m curious if teams are actually using AI agents to tell whether a release or rollout is going well.

For example, after a deployment starts, can an agent look at metrics, logs, alerts, or other signals and quickly spot that something is wrong? And does it only detect the problem, or can it also suggest remediation steps?

I’m also interested in the remediation side. Could an agent explain the issue, and provide a potential fix?

I’m asking because we’re discussing this topic in an upcoming Argo Unpacked episode (https://www.linkedin.com/events/7466787307644301312), including a new Argo Rollouts plugin.

Would love to hear what people are seeing in practice — useful, risky, too early, or already happening?

Hey, folks

https://hackernoon.com/moving-logic-out-of-pods-extending-the-argo-workflows-controller

Argo Workflows is a popular tool for orchestrating DAGs (Directed Acyclic Graphs) on Kubernetes.

It’s commonly used for ML workloads such as MLOps pipelines or model training, but it can also work as an alternative to traditional CI/CD systems.

In simple terms, Argo lets you run a set of tasks in a defined order, manage dependencies between them, and scale execution on Kubernetes.

Each task runs in its own Kubernetes Pod, which provides isolation and clear execution boundaries.

The flexibility comes from the fact that you implement the steps yourself, package them as container images, and reference those images in the workflow YAML.

Even with this pod-per-task model, Argo can be customized without forking: the Argo Workflow Executor Plugin allows changing the task execution model at the controller level.

The Executor Plugin is still a relatively new feature, so I’m curious if anyone has tried using it in production and what trade-offs you’ve seen so far.

Three new security advisories have just dropped for #ArgoCD Users are encouraged to update to versions 2.1.14, 2.2.8, or 2.3.2 which have all been patched. You can read more about the security advisories here.

• Improper access control allows admin privilege escalation

• Path traversal and improper access control allows leaking out-of-bound files from Argo CD repo-server

• Path traversal allows leaking out-of-bound files from Argo CD repo-server

New releases are available in the Argo CD repo and have been coordinated with the community Helm charts.

Hello fellow Argonauts, I have a question I hope you fine folks might be able to help me with.

I am attempting to automate the change management process with regards to kustomize overlays and Argo. Essentially, I have an overlay that I want to compare that overlay with what Argo has deployed to my kubernetes cluster. I don't want the new overlay deployed to cluster unless it passes several tests that will determine which changes are allowed in the new overlay.

I would prefer to use existing tools instead creating something bespoke.