Author: Arthur Schmunk / Source: The Next Web
You’ve seen DevOps, and DevSecOps, and maybe even NoOps. But if you haven’t already, you’re going be hearing a whole lot more about GitOps.
As an indicator, four of the sessions at the upcoming KubeCon are about GitOps. You might not know what GitOps is, but if you’re developing software, there’s a good chance you’re already doing it.
What’s GitOps? And do we really need another software development buzzword?
Well, GitOps is really the culmination of a few different trends in software development, deployment, and operation taken to their logical conclusion. Together, they create a new way of working with new powerful synergies.
The term GitOps was coined by Alexis Richardson at Weaveworks, where it was focused on running Kubernetes-based infrastructures.
But GitOps is a much bigger idea than just Kubernetes; it’s a philosophical approach to developing and deploying software that can be applied more broadly by any company which runs its own code on its own infrastructure with its own configurations.
Single Source of Truth
The first principle of GitOps, and perhaps the one most emphasized by Alexis Richardson is that in GitOps, Git (or the version control system of your choice!) is the “single source of truth” for application code, infrastructure and configurations.
This is a term from Information Theory but essentially it means this: Git is always right. It’s the last word. You can understand the whole system by looking at Git and without looking everywhere else. It has all the ingredients right there.
Everything as Code
Those ingredients include the code of the applications, of course, and the various other code components that applications use like libraries and frameworks. But they also include other types of code. Configurations, once stored in databases, are now codified in YAML files in Git repositories. In many cases, infrastructure, too, is defined in code now, whether virtual servers, Docker images or Kubernetes clusters. Taken together, these different sorts of code are able to describe the whole system.
CI/CD Automation
That’s where the magic kicks in. Automated test, build and deployment tools take over the CI/CD process,…
The post Already learned DevOps? Great, now it’s time for GitOps appeared first on FeedBox.