High Availability in Argo CD

When single node is disabled, Argo CD is configured to have Horizontal Pod Autoscaler (HPA) for autoscaling with two minimum replicas and a Pod Disruption Budget (PDB) to facilitate availability during node replacement. Note that Argo CD requires at least three different nodes and does not support IPv6 only clusters. For more information, please see the official Argo CD documentation on high availability.

However, some components of Argo CD cannot be duplicated. For example, the argocd-dex-server uses an in-memory database, and trying to copy that instance would create inconsistent data. The application-controller only supports sharding at the cluster level.