Argo CD and Flux GitOps

Retired

No longer on the radar

We removed this entry in the September 2026 release. Retiring is not a recommendation against it — it means the radar no longer needs a separate opinion here. The write-up below is kept as it was last published and is no longer maintained.

This decision is now covered by:

Overview

Argo CD and Flux continue as the dominant GitOps controllers for Kubernetes, now commonly orchestrating AI workloads, model servers, and agent sandboxes from Git-declared state (Argo CD, Flux).

Trial is less about the tools (often already Adopt for infra) and more about GitOps patterns for prompt configs, model versions, and policy bundles with signed commits and promotion flows.

Sources