to change the state you need to perform a Git operation such as creating a commit or opening a pull request Specifically for Kubernetes, GitOps says that you must not use `kubectl` to change the cluster mixing CI with CD and you admit that GitOps does not cover this scenario. 2. “We open a new pull request to the other environment.” This means that you are forced to have different Git branches for open/close 10 pull requests each time you do a release. ● 10 Git repositories. This means that you need to write your own solution that copies commits between the repositories (or uses Pull Requests between

CI/CD Traditional CI/CD Workflows Where does GitOps fit in? Operations via Pull Request Summary 14 Chapter 2–Tools of the Trade Infrastructure as Code History of Infrastructure to GitOps | 11 Pulled Automatically The third principle states: Software agents automatically pull the desired state declarations from the source. This principle is where GitOps starts to differentiate 12], the recommended way to trigger deployment is by submitting a pull request; in GitLab [1.13] it’s by submitting a merge request (the same idea with a different term). Once merged, the change will

Image Registry Kubernetes CI CD The GitOps Application Delivery Model Pull Request Push Pull Push Pull Pull Request 9 Source Git Repository Image Registry CI The GitOps Application Delivery Repository Image Registry Kubernetes The GitOps Application Delivery Model on OpenShift Pull Request Push Pull OpenShift Builds 12 Automate building container images using Kubernetes tools GENERAL app namespaces Flexible Deployment Strategies Central Hub (Push) Application Scoped (Pull) Cluster Scoped (Pull) OpenShift OpenShift Auth Registry Networking Storage Install Operators Namespaces

organization. Not only are your continuous integration and continuous deployment pipelines all driven by pull request, but your operations tasks are also fully reproducible through Git. 6. Stronger Security Guarantees All changes can be triggered, stored, validated and audited in Git Ops changes can be made by pull request including rollbacks Ops changes can be observed and monitored Since all of your developers can also use the same workflow to make infrastructure changes by creating issues, and reviewing pull requests. GitOps allows you to roll back any kind of change made in your cluster. In addition to

simple pull request. GitOps allows you to create and manage your entire software stack through Git and treat your servers as your source code. Every change and configuration is done through a pull request where your design stays in Git, and everything is in Git. Your production or staging environment will pull from Git continuously to implement whatever change you want to make, to ensure you have no drift for the SREs to easily perform upgrades on these configurations and to introduce controls through pull requests. The result is a standard cluster development platform that spans environments with security

infrastructure as code and version control them via Git. Whenever a new change is required, a pull request with the new change is created, executing the CI/CD pipeline to provision or modify the infrastructure Troubleshooting Auditing Rollbacks Changes are automatically applied when approved When a pull or merge request is made, it will be verified and then approved since all the changes are stored in Git. Furthermore will: Declare the infrastructure as code. 1. Push the code to a Git repository. 2. Create a pull request. 3. After that, this code can be reviewed and scrutinized by another team member and finally

your entire system in Git means that your development team uses familiar Git-based workflows and pull requests to deploy both application and infrastructure changes to Kubernetes. With the entire and declarative application stacks. Every developer on your team is familiar with Git and can make pull requests. Now, they can use Git to accelerate and simplify application deployments to Kubernetes Figure 2 Here is a typical developer workflow for creating or updating a new feature: 1. A pull request for a new feature is pushed to GitHub for review. 2. The code is reviewed and approved by a

pipeline, developers do not need to learn to use new tools. They can work in a world they know, using pull requests to accelerate deployment and operations tasks. The benefits for development teams include Kubernetes itself, right across your organization. Not only will all your CI/CD pipelines be driven by pull request, but operations tasks will also be fully reproducible through Git. 6. Stronger security guarantees application developers access to a GitOps-based platform, they can use familiar tools and workflows (like pull requests) to optimize their efficiency. And because security and compliance are baked into the process

prior time period ● Accessible - Changes only require a pull request ● Git as a system of record for the desired state of configuration ● Pull requests drive all application & infrastructure changes

through the tools they work in everyday. Changes are automatically applied to the cluster once a Pull Request is approved and merged. Changes are handled by reconcilers that look for discrepancies between compliance just by using Git. Standardize workflows Establish an end-to-end CI/CD workflow driven by pull requests and fully reproducible through Git. Embed security Leverage Git’s correctness and strong