By IT Brew Staff
less than 3 min read
Definition:
GitOps rests on three “pillars”: infrastructure-as-code (IaC), pull and merge requests to update infrastructure and keep configurations up-to-date, and continuous integration and continuous delivery and deployment (CI/CD).
As the name implies, GitOps takes quite a bit from DevOps, including the focus on CI/CD and collaboration. GitOps hinges on the use of Git pull requests to install, update, and decommission live infrastructure and apps; to start, IT teams decide on the desired final state of the system, and set up the tools and procedures necessary to track that system’s current state. GitOps also depends on a GitOps operator, which triggers when a pull request activates the GitOps pipeline; the operator then syncs the current state of the repository with that of the orchestration system, which actually executes GitOps procedures.
When executed correctly, GitOps confers a number of benefits, including the standardization of the IT team’s infrastructure and application-development workflows, coding consistency across multi-cloud and on-premises environments, and more reliability and visibility with software version control. Because Git quickly allows developers and other IT pros to roll back a software change to its previous state, GitOps can prove an excellent way for IT teams to experiment with configurations and roll out new infrastructure without worrying about making the wrong move with vital, complicated systems.
