Overview

[!NOTE] This section contains information on upgrading Argo CD. Before upgrading please make sure to read details about the breaking changes between Argo CD versions.

Argo CD uses semver-like versioning that ensures the following rules:

The patch release does not introduce any breaking changes. So if you are upgrading from v1.5.1 to v1.5.3 there should be no special instructions to follow.
The minor release might introduce minor changes with a workaround. If you are upgrading from v1.3.0 to v1.5.2 please make sure to check upgrading details in both v1.3 to v1.4 and v1.4 to v1.5 upgrading instructions.
The major release introduces backward incompatible behavior changes. It is recommended to take a backup of Argo CD settings using the disaster recovery guide.

After reading the relevant notes about possible breaking changes introduced in a new Argo CD version, use the following command to upgrade Argo CD. Make sure to replace <version> with the required version number:

Non-HA:

bash

kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/<version>/manifests/install.yaml

HA:

bash

kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/<version>/manifests/ha/install.yaml

[!NOTE] The --server-side --force-conflicts flags are required because some Argo CD CRDs exceed the size limit for client-side apply. See the getting started guide for more details.

[!WARNING] Even though some releases require only image change it is still recommended to apply whole manifests set. Manifest changes might include important parameter modifications and applying the whole set will protect you from introducing misconfiguration.

<hr/>