#argocd

A CVE dork returning zero is a statement about the index, not about exposure. What 62,245 Argo CD fingerprints, 25,097 on port 443 and an empty CVE match actually tell you.

On October 7, 2026, Argo CD released six security advisories, four of which had a CVSS score of 9.9 – three of the critical vulnerabilities lack a CVE number. This article explains why the repo server

Auto-sync and self-heal are usually presented as unambiguous wins. They are — right up until...

Somebody on r/kubernetes asked a plain question this week: how do you test your Argo CD addons...

With the documented argoproj.io_Application health check, Argo CD v3.5.3 started wave 2 while a child missing a resource read Healthy; on v3.3.14 that child read Missing and the gate held.

一句話結論：把 ArgoCD 裝好之後，只手動 apply 一個 root Application，讓它掃描 Git 裡的某個目錄；之後要新增、修改、移除任何 App，都只要改 Git，不用再碰...

Shared Responsibility in Argo CD: Who Owns Each Part of CVE-2026-77459 and Its Siblings ...

From Jenkins credential errors to a working pipeline, Kubernetes deployment, and automated GitOps...

I wrote the longer version, with more on each Argo project and my prep timeline, on my blog. Daily...

Patching Argo CD to v3.5.4, v3.4.10, v3.3.15 or v3.6.0-rc2: A Migration Checklist ...

Canary and blue-green releases, automated analysis, and v1.10.0: How Argo Rollouts makes releases on Kubernetes measurable and safe – and where it differs from Flagger.

In September I renamed an Argo CD application and took our payments API down for six minutes. We...