GitOps and Kubernetes delivery
What is Kargo? An introduction to Akuity's continuous promotion layer for Kubernetes
Kargo is a continuous promotion orchestration layer that complements Argo CD for Kubernetes. It automates multi-stage application promotion using GitOps principles. Its aim is to remove the need for custom automation or CI pipelines to move a change from one stage to the next.
- Tool
- Kargo
- Made by
- Akuity
- Official site
- kargo.io
- Category
- GitOps and Kubernetes delivery
Who makes Kargo
Kargo is made by Akuity. It is built and maintained by the creators of Argo, the project family that Argo CD belongs to.
The official website is linked below this page.
Official website: kargo.io
What Kargo is for
Kargo handles the step that comes after a change is built: moving it through environments. It promotes changes from one environment to the next, using one stage's source of truth as the basis for the next. This keeps each promotion tied to what was already running in the previous stage.
Kargo aims to remove the need for custom automation or CI pipelines for stage-to-stage promotion. Teams that script promotions by hand, or stretch a CI pipeline to cover them, get a purpose-built layer instead.
Kargo also lets users define and manage relationships between application instances deployed across environments. Those relationships describe how a change should flow between, for example, a development instance and a later one.
Who Kargo is for
The vendor names developers, teams using Argo CD on Kubernetes, and all team members as the audience. The clearest fit is a team that already runs Argo CD and needs a structured way to carry changes across several environments.
Because Kargo gives a view of changes across every environment, it is also relevant to people who do not write the manifests but need to know what is running where.
Notable capabilities
Kargo concentrates on promotion rather than on building or syncing applications. Its capabilities are listed below.
- Promotion orchestration: it automates progressive rollouts across the application lifecycle and integrates with existing systems such as Argo CD.
- Customizable pipelines: promotion pipelines can be tailored to specific workflows.
- Environment relationships: users define and manage how application instances across environments relate to each other.
- Cross-environment visibility: it provides a view of changes across every environment.
- Guardrails: built-in processes and guardrails govern transitions between environments.
- Configuration as code: it promotes configuration changes the way container images are promoted.
- Multiple artifact sources: it tracks updates from git artifacts, container images, Helm charts and more.
- Rollback: developers can promote container images, Kubernetes manifests and Helm charts, with rollback capabilities.
How Kargo fits GitOps and Kubernetes delivery
In GitOps and Kubernetes delivery, a tool such as Argo CD reconciles a cluster with a desired state held in git. Kargo sits alongside it and addresses a different question: how a change becomes the desired state of the next environment. It is described as a native CD solution designed specifically for Kubernetes environments.
In the wider field of CI/CD and deployment platforms, CI systems typically build and test artifacts, and delivery tooling takes over from there. Kargo occupies the later part of that path, the movement between stages, and works with existing systems rather than replacing them.
Frequently asked questions
What is Kargo used for?
Kargo is used to automate multi-stage application promotion on Kubernetes using GitOps principles. It moves changes from one environment to the next, using one stage's source of truth as the basis for the next.
Who develops Kargo?
Kargo is made by Akuity and is built and maintained by the creators of Argo.
Does Kargo work with Argo CD?
Yes. Kargo is a continuous promotion orchestration layer that complements Argo CD and integrates with existing systems such as Argo CD.
What can Kargo promote?
Developers can promote container images, Kubernetes manifests and Helm charts, with rollback capabilities. Kargo tracks updates from git artifacts, container images, Helm charts and more.
Do I need custom CI pipelines to promote between stages with Kargo?
Kargo aims to remove the need for custom automation or CI pipelines for stage-to-stage promotion.
Deployelm is independent and is not affiliated with Akuity. Product names belong to their owners. Features change; confirm details on the official website.