Core components of a GitOps workflow

Here are three core components of a GitOps workflow:

Infrastructure as Code (IaC): GitOps relies on defining and managing infrastructure configurations as code in a Git repository. All infrastructure details, including servers, networks, databases, and applications, are described in code files, typically using formats like JSON or YAML. The sources emphasize using declarative code, where you define the desired end state of the infrastructure rather than step-by-step instructions.

Merge Requests (MRs): Changes to the infrastructure are proposed and implemented through merge requests. These MRs act as a central point for collaboration, review, and approval of infrastructure modifications. They provide a clear audit trail, allowing teams to track who made what changes and when. The sources suggest setting guidelines for code reviews, including a minimum number of reviewers, to ensure quality and prevent errors.

Continuous Integration and Continuous Delivery (CI/CD): GitOps leverages CI/CD pipelines to automate the deployment and management of infrastructure. When changes are merged into the main branch of the Git repository, the CI/CD pipeline automatically applies these changes to the target environment. The sources highlight the importance of using CI/CD to enforce infrastructure as code principles, automatically provisioning and updating resources based on the code definitions. The CI/CD pipeline can also include automated tests and validation steps to ensure the infrastructure code is correct and meets desired standards.