发布日期: 2026-02-22
版本号: v3.3.2

在升级至Argo CD v3.3.2版本前，请务必先阅读官方升级指南，了解可能的破坏性变更。对于使用Argo CD管理自身安装的用户，必须在管理该安装的Argo CD Application上启用ServerSideApply=true同步选项才能成功升级。此前在3.3.0和3.3.1版本中出现的“failed to perform client-side apply migration”问题已在本版本中修复。若用户此前已升级至3.3.0或3.3.1并应用了临时解决方案ClientSideApplyMigration=false，现在必须移除该设置以恢复默认的迁移行为，否则可能导致后续字段管理器冲突。本版本还包含针对客户端应用迁移时管理字段的修复以及相关文档更新。安装可使用非高可用或高可用配置的命令快速进行。所有容器镜像和CLI二进制文件均经过签名并符合SLSA三级规范，可验证其来源。

更新内容 （中文）

[!IMPORTANT] 在将所有类型的 Argo CD 安装升级到此版本之前，请先阅读升级指南：
https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

升级管理自身的 Argo CD

若您有一个 Argo CD Application 用于管理您的 Argo CD 安装，则必须在此 Application 上启用 ServerSideApply=true 同步选项才能成功升级。

版本 3.3.0 和 3.3.1 中存在的 failed to perform client-side apply migration 问题已在本版本中解决：https://github.com/argoproj/argo-cd/issues/26279

对于先前已升级到 Argo CD 3.3.0 或 3.3.1，并在管理其 Argo CD 的 Application 上应用了临时解决方案 ClientSideApplyMigration=false 同步选项的用户，需要移除此设置以恢复执行迁移的默认行为。 移除 ClientSideApplyMigration=false 同步选项的原因是，它可能在后续时间点导致 Argo CD K8s 字段管理器与其他字段管理器发生冲突。

更多详细信息请参见：
https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

快速开始

非高可用：

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/install.yaml

高可用：

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/ha/install.yaml

发布签名与来源证明

所有 Argo CD 容器镜像均由 cosign 签名。 符合 SLSA Level 3 规范的容器镜像和 CLI 二进制文件会生成来源证明。请参阅 文档 了解验证方法。

发布说明博客文章

有关此版本关键变更和改进的详细分析，请查看官方博客文章

升级

如果从不同的次版本进行升级，请务必阅读升级文档。

变更日志

错误修复

  • 67c23193c4dc23defb4cad555ba975cf501ba1b0: 修复: 使用 csapgrade 修补 managedFields 以进行客户端应用迁移 (cherry-pick #26289 for 3.3) (#26516) (@argo-cd-cherry-pick-bot[bot])

文档

  • 1bf62aea1991a772769b110d8a10e8d56a3c1eb2: 文档: 指导在 3.3.2 中启用 ClientSideApplyMigration (cherry-pick #26547 for 3.3) (#26549) (@argo-cd-cherry-pick-bot[bot])

完整变更日志: https://github.com/argoproj/argo-cd/compare/v3.3.1...v3.3.2

更新内容 （原始）

[!IMPORTANT] Before upgrading all types of Argo CD installations to this release, please read the upgrade guide first: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/3.2-3.3/#breaking-changes

Upgrading Argo CD which is managing itself

Users who have an Argo CD Application that manages their Argo CD installation, must enable ServerSideApply=true sync option on this Application in order for the upgrade to succeed.

The issue with failed to perform client-side apply migration that existed on version 3.3.0 and 3.3.1 has been solved in this release: https://github.com/argoproj/argo-cd/issues/26279

For users who have previously upgraded to Argo CD 3.3.0or 3.3.1 and applied the temporary remediation of ClientSideApplyMigration=false sync option on the Application that manages their Argo CD, are required to remove this setting to restore the default behavior of performing the migration. The reason for removing the ClientSideApplyMigration=false sync option is that it may cause conflicts between Argo CD K8s field manager and other field managers at a later point in time.

More details here: https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#client-side-apply-migration

Quick Start

Non-HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/install.yaml

HA:

kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.3.2/manifests/ha/install.yaml

Release Signatures and Provenance

All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the documentation on how to verify.

Release Notes Blog Post

For a detailed breakdown of the key changes and improvements in this release, check out the official blog post

Upgrading

If upgrading from a different minor version, be sure to read the upgrading documentation.

Changelog

Bug fixes

  • 67c23193c4dc23defb4cad555ba975cf501ba1b0: fix: use csapgrade to patch managedFields for client-side apply migration (cherry-pick #26289 for 3.3) (#26516) (@argo-cd-cherry-pick-bot[bot])

Documentation

  • 1bf62aea1991a772769b110d8a10e8d56a3c1eb2: docs: instruct to enable ClientSideApplyMigration in 3.3.2 (cherry-pick #26547 for 3.3) (#26549) (@argo-cd-cherry-pick-bot[bot])

Full Changelog: https://github.com/argoproj/argo-cd/compare/v3.3.1...v3.3.2

下载链接