mirror of
https://github.com/argoproj/argo-cd
synced 2026-04-21 17:07:16 +00:00
70 lines
2.8 KiB
Markdown
70 lines
2.8 KiB
Markdown
# 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](./1.3-1.4.md) and [v1.4 to v1.5](./1.4-1.5.md)
|
|
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](../disaster_recovery.md).
|
|
|
|
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](../../getting_started.md#1-install-argo-cd) 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/>
|
|
|
|
- [v3.4 to v3.5](./3.4-3.5.md)
|
|
- [v3.3 to v3.4](./3.3-3.4.md)
|
|
- [v3.2 to v3.3](./3.2-3.3.md)
|
|
- [v3.1 to v3.2](./3.1-3.2.md)
|
|
- [v3.0 to v3.1](./3.0-3.1.md)
|
|
- [v2.14 to v3.0](./2.14-3.0.md)
|
|
- [v2.13 to v2.14](./2.13-2.14.md)
|
|
- [v2.12 to v2.13](./2.12-2.13.md)
|
|
- [v2.11 to v2.12](./2.11-2.12.md)
|
|
- [v2.10 to v2.11](./2.10-2.11.md)
|
|
- [v2.9 to v2.10](./2.9-2.10.md)
|
|
- [v2.8 to v2.9](./2.8-2.9.md)
|
|
- [v2.7 to v2.8](./2.7-2.8.md)
|
|
- [v2.6 to v2.7](./2.6-2.7.md)
|
|
- [v2.5 to v2.6](./2.5-2.6.md)
|
|
- [v2.4 to v2.5](./2.4-2.5.md)
|
|
- [v2.3 to v2.4](./2.3-2.4.md)
|
|
- [v2.2 to v2.3](./2.2-2.3.md)
|
|
- [v2.1 to v2.2](./2.1-2.2.md)
|
|
- [v2.0 to v2.1](./2.0-2.1.md)
|
|
- [v1.8 to v2.0](./1.8-2.0.md)
|
|
- [v1.7 to v1.8](./1.7-1.8.md)
|
|
- [v1.6 to v1.7](./1.6-1.7.md)
|
|
- [v1.5 to v1.6](./1.5-1.6.md)
|
|
- [v1.4 to v1.5](./1.4-1.5.md)
|
|
- [v1.3 to v1.4](./1.3-1.4.md)
|
|
- [v1.2 to v1.3](./1.2-1.3.md)
|
|
- [v1.1 to v1.2](./1.1-1.2.md)
|
|
- [v1.0 to v1.1](./1.0-1.1.md)
|