<img src="https://secure.insightfulcloudintuition.com/268016.png" style="display:none;">
Skip to content
akuity.iostaticlogo-4e82a3d473fae8e1041846a7b9e1d3cb-1
Akuity.io

[On-Demand Webinar]

Fleet Management for Kargo Enterprise:

Ship one release to hundreds of targets in controlled waves

Jesse Suen, co-creator of Argo CD and Kargo and Akuity's co-founder and CTO, previews Fleet Management for Kargo Enterprise. Instead of one Kargo stage per cluster, a single promotion rollout fans out to every matching target with a concurrency limit and a failure threshold, so a bad change stops before it reaches the rest of the fleet. Jesse explains targets, target sets, and promotion rollouts, then promotes cert-manager live across a 400-cluster demo fleet. Q&A covers Argo CD ApplicationSets, rollback, Argo Rollouts, per-target verification, and what happens when the target list changes mid-rollout.

Key Takeaways:

  • Per-cluster stages stop scaling past a few dozen clusters. One stage for many clusters means a risky all-at-once update with no per-cluster visibility. One stage per cluster means hundreds of manual promotions and pipeline edits every time a cluster is added.
  • Targets come from your inventory, not hand-written manifests. A target set generates targets from EKS, GKE, or AKS cluster lists, files in Git, or Argo CD applications by label. Add or retire a cluster at the source and Kargo picks it up, so managing 1,000 clusters takes the same pipeline as managing 10.
  • A promotion rollout is a promotion of promotions. You approve once and get one audit record, and each target gets its own individual promotion. Stages select targets by label, for example per environment and per geography.
  • Concurrency limits and failure thresholds stop bad rollouts early. In the demo, a prod stage of 112 targets updates 20 at a time with a 5% failure threshold. A few failures don't block the rollout; crossing the threshold halts it, and you can retry only the targets that failed or never ran.
  • Fleet Management complements ApplicationSets. ApplicationSets decide which Argo CD apps exist (400 clusters x 6 add-ons = 2,400 apps); targets decide where a release rolls out. Progressive syncs only order Argo CD syncs, while Kargo promotions can write to Git, run Terraform, or call custom steps.

Helpful Links: