Sometimes I think Git is a bit like that.

We all know Git.

Its the foundation of the modern software development workflow.

GitOps has been ‘controversial’ — but the truth is your organization needs it

GitOps unleashes that other 90%.

Speed, collaboration, and consistency

40% off TNW Conference!

In my opinion and experience there areplentyof reasons to get evangelical about GitOps.

One of the most oft-quoted arguments points out that GitOps is inherently fast.

But this isnt necessarily a unique advantage to GitOps; weve had automated delivery for years now.

GitOps requires all system infrastructure to be described declaratively.

The definition sits in a repository, surrounded by a flock of automated procedures responsible for deployment and integration.

From the outset, a huge chunk of the scope for human error is excised.

But thats only part of it.

Make a mistake in one of your configurations?

Just roll back to the last working version and redeploy.

Spotted some anomalous behavior in a container?

Look at the code and see what changed between the current version and the last known working version.

Its also worth noting that Git is, by design, inherently collaborative.

What GitOps isnt

Its fair to say that GitOps has its share of detractors.

Vanilla Git will only take you so far when it comes to building a GitOps workflow.

Take, for example, secrets management.

It just isnt secure.

Right now, theres no way to natively inject these secrets into a deployment from within Git.

That results in extra work, but its hardly an insurmountable problem.

Thats true, but also missing the point somewhat.

New configurations can be tested in separate branches, before theyre ultimately merged into the main version.

Mistakes can be rolled-back.

And you’re able to contrast different versions of the same configuration to identify where problems crop up.

Another complaint says GitOps is overly centralized.

This isnt a vice, but rather a virtue.

Practical matters follow closely behind.

Eventually, you build your stack around your own needs: from deployment and auditing to secrets management.

Automation in this space is nothing new.

And the universal familiarity of Git itself means its not hard to hit the ground running.

In short, GitOps will allow your team to work faster, and with greater precision and consistency.

So, what are you waiting for?

Also tagged with