Argo
v3.3.2CI/CD & App DeliveryArgo CD v3.3.2 fixes the critical client-side apply migration issue that affected self-managed installations in v3.3.0/v3.3.1, requiring specific upgrade steps for users managing Argo CD with itself.
breakingEnable ServerSideApply for Self-Managed Installations
If you have an Argo CD Application managing your Argo CD installation, you must enable `ServerSideApply=true` sync option on that Application before upgrading to v3.3.2. This is required for the upgrade to succeed and prevents apply migration failures.
breakingRemove Temporary ClientSideApplyMigration Setting
If you previously upgraded to v3.3.0/v3.3.1 and set `ClientSideApplyMigration=false` as a workaround, remove this setting after upgrading to v3.3.2. Keeping it may cause field manager conflicts with other Kubernetes controllers.
enhancementSafe Upgrade Path for Previously Affected Users
Users affected by the v3.3.0/v3.3.1 client-side apply migration bug can now safely upgrade to v3.3.2. Follow the upgrade guide carefully and test the upgrade process in a non-production environment first, especially for self-managed installations.
Key changes (4)
- Fixed client-side apply migration failure that prevented successful upgrades in v3.3.0/v3.3.1
- Resolved conflicts between Argo CD field manager and other Kubernetes field managers
- Updated documentation to clarify upgrade requirements for self-managed installations
- Maintained SLSA Level 3 provenance and cosign signatures for all container images