Argo CD | v3.4.3

Argo CD v3.4.3 released on 28-05-2026


Argo CD v3.4.3 is out now. It provides immediate installation steps for both non‑HA and HA deployments and ships signed container images plus provenance metadata meeting SLSA Level 3 for verifiable releases.

Refer to the manifests, the signed‑releases documentation, the upgrading guide and the full changelog on the Argo CD project pages for installation commands, verification steps and a full breakdown of fixes and changes.

What’s in this release

  • Quick start and installation: create the argocd namespace and apply the release manifests with server‑side apply and –force-conflicts for non‑HA (manifests/install.yaml) and HA (manifests/ha/install.yaml) deployments.
  • Security: all container images are signed with cosign and provenance metadata is produced for images and CLI binaries that meet SLSA Level 3; documentation links explain how to verify signatures and provenance.
  • Changelog highlights and bug fixes: immediate return from argocd app wait when the app is already in the desired state, several UI fixes, honoring repo depth in fetch/change detection, multiple nil‑check and race‑condition fixes, label truncation for deletion‑hook resources, and a dependency bump (redoc/dompurify v3.4.0) addressing CVE‑2026‑41240.

Upgrade notes

  • No breaking changes are listed in the release notes; if upgrading between minor versions consult the official upgrading documentation before proceeding: Upgrade guide.
  • There are no explicit rollback instructions in the notes; keep the release manifests and the full changelog handy if you need to revert: Full changelog.

Try the release and share your experience or any issues on the Argo CD project pages so others can benefit from your notes.

Related posts

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...

restic | v0.19.1

restic v0 19 1: safer FUSE mounts and mountpoint checks, robust backup source and exclude handling, clearer CLI JSON output, Windows SFTP deletion fixes