GigaOm Radar for GitOpsv3.0

1. Executive Summary

Enabled by infrastructure as code (IaC), GitOps takes advantage of the “as code” aspect to move configuration information into version control systems. In the most evolved GitOps implementations, rolling out a new release is as easy as doing a commit to version control.

A GitOps approach can provide a range of benefits to organizations. The toolset used to manage applications, infrastructure, and operational elements should be simplified. Changes are driven by the source control system, so staff can drive many downstream actions via source control tools. Managing infrastructure and operational resource definitions in source control also provides additional semantics and controls for these elements compared to a non-GitOps approach. For example, infrastructure configurations can be branched, versioned, reviewed, tagged, refactored, validated, unit-tested, and so on in the same way that application code is.

All changes are traceable and auditable, can have additional context available from commit messages, and can have access or other policy rules applied to them. Organizations adopting GitOps may also benefit from increased agility and reliability because they can safely ship new code, scale, and adapt more quickly. Finally, GitOps allows organizations to improve their security posture as processes are simplified and codified and attack surfaces reduced.

Because of the evolution of FluxCD and ArgoCD, the market is increasingly focused on the value add of policy management and creation. Our analysis considers this market focus.

A GitOps toolchain assumes a version control tool, CI/CD tools, and centralized reporting. While not required, GitOps is far more useful with container registries and change control processes over repositories, though traditional infrastructure cannot be ignored.

This is our third year evaluating the GitOps space in the context of our Key Criteria and Radar reports. This report builds on our previous analysis and considers how the market has evolved over the last year.

This GigaOm Radar report examines six of the top GitOps solutions and compares offerings against the capabilities (table stakes, key features, and emerging features) and nonfunctional requirements (business criteria) outlined in the companion Key Criteria report. Together, these reports provide an overview of the market, identify leading GitOps offerings, and help decision-makers evaluate these solutions so they can make a more informed investment decision.