How to Use GitOps

In many organizations, engineers spend too much time waiting for infrastructure change requests. Limited resources cause infrastructure-dependent changes to lag behind, increasing development demand. GitOps presents one solution by repurposing your organization’s existing Git pull-request workflows to permit infrastructure-oriented teams to safely democratize changes.

Distributing control down to the dependent teams improves transparency, velocity, predictability, auditability, and more. In a GitOps world, all infrastructure elements are defined as code. Changes are proposed in the code repository with the same mechanism as developers working on traditional applications. When the changes are approved and committed, automation validates the change and deploys them into production safely.

Developers are already familiar with your existing Git pull-request workflow, which can make it easy for them to switch to and from the application code they are already developing. Other benefits include collaborative discussions, ephemeral environments, formal change traceability, automated testing, and human-in-the-loop approval—all enabling your infrastructure changes.

In this paper we’ll define GitOps, explain where it is best applied and why, and make suggestions on adopting this practice in your organization.

What's inside

• Clear Guidance — This paper focuses on three specific factors to consultancy success: accountability, dependency, and disruption of change.
• Expert Authors — This paper is written by experienced leaders across industries who have worked with successful partnerships with consultants across multiple industries.
• Case Studies — This paper illustrates both successful and not successful consultant experiences in real-life organizations across industries.
• All Levels — Change Agents can come from anywhere on the org chart. This paper directly provides guidance on how to lead change no matter your role or title.