GitOps is rapidly becoming a best practice approach to delivering cloud-native applications and is also a tool framework for automating best practices. In a broader sense, GitOps can be seen as a further development of software-defined infrastructure approaches, as these are increasingly automated and can therefore be used beyond cloud-native applications.
At its core, GitOps links two concepts:
- Manage infrastructure information through a version control system like Git
- Closing the circle between operational infrastructure management and a software-defined infrastructure definition
Modern version control systems and approaches are natively geared towards managing configuration files associated with software-defined infrastructure. Today these files are standardized using YAML and Terraform, which increases the need to store them in a common repository of code. This trend has been accelerated by hyperscalers like AWS and Azure, which advocate Infrastructure as Code (IaC) best practices.
However, GitOps is more than just storing IaC files in version control. It closes the loop between declaration, deployment, and operations and enables transparency, manageability, and security. This closed loop allows configuration changes to be monitored in the live environment to drive updates to the “last known good” configuration information and to ensure that the desired and actual configurations stay in sync.
Note that while this report focuses primarily on Kubernetes, the model advocated by GitOps is growing to cover other areas of enterprise technology usage in cloud, enterprise, telecommunications, edge, and even in policy and process management and AI. While GitOps solutions today – the focus of this report – are geared towards cloud-native Kubernetes environments, we expect the principles, practices, and tools to extend more broadly to software-defined application architectures.
So read this report
This GigaOm report is one of a series of documents that IT organizations can use to evaluate competing solutions in the context of clearly defined functions and criteria. For a fuller understanding, be sure to read the following reports:
Report on the main criteria: A detailed market sector analysis that assesses the impact of key product characteristics and criteria on key solution characteristics such as scalability, performance and total cost of ownership that influence purchase decisions.
GigaOm Radar Report: A forward-looking analysis that shows the relative value and progress of vendor solutions along multiple axes based on strategy and execution. The Radar report provides a breakdown of what each vendor in the industry has to offer.
Provider profile: An in-depth vendor analysis, building on the framework developed in the Key Criteria and Radar Reports, to assess a company’s exposure to a technology sector. This analysis contains forward-looking guidelines for strategy and product.