GitOps has emerged as a key technology in the cloud native computing space over the last few years. Research into delivery velocity (from DORA and others) has shown that speeding up software delivery is closely correlated with business success. GitOps is an approach for building incredibly robust and repeatable continuous delivery pipelines.
While every organization is different, a number of common patterns have emerged. The GitOps Maturity Model shows a simple four step process that organizations commonly transition through as they move from using GitOps to manage single clusters and applications to managing large scale deployments of hundreds or even thousands of clusters.
This is not to say that everyone should take the same path - some organizations may wish to jump straight into a higher level of the maturity model. Others may decide that they don’t need to progress to the higher levels. Whether or not you follow the same path, it is useful to understand the common progression: the reasons why deployments move through this journey and the benefits of increasing GitOps maturity.
In this whitepaper we outline a maturity model based on experiences working with leading edge organizations who are implementing GitOps delivery pipelines.
What you will learn in this white paper:
- A detailed explanation of what each level of GitOps maturity looks like in practice. Using this, you can identify which level your organization falls into.
- The business benefits of each level and how they apply to different teams in an organization.`
- How your organization can move to a higher level of GitOps and what it would look like when you get there.
- Ways you can improve your organization's performance against DORA metrics to achieve faster and more agile deployments.