In the case of GitOps tooling, we can handle the promotion mechanism in a different number of ways, such as introducing an automation mechanism for Pull Requests (more on this in the next section) or previous environment (e.g. production to QA in order to examine a bug) ● has a configuration mechanism in place to define multiple version of the same environment (i.e. for different geographical regions) storage mechanism for all secrets, but also a comprehensive way on how to group them according to each environment and how to pass them in the respective cluster. The underlying mechanism is not

code to Git, and then, further deployment and tweaks would be taken care of by an automated mechanism. Since Kubernetes and many other cloud-native technologies are almost entirely declarative, perfect for GitOps-style deployment workflows: • Automation: Kubernetes provides a built-in mechanism for automating the deployments. A Kubernetes cluster applies a set of changes in the correct

CI/CD pipeline.) The differentiating factor of a GitOps pipeline is the GitOps operator. This mechanism sits between the pipeline and the infrastructure platform, acting as a middleman for facilitating

before detecting and correcting drift. The GitOps controller acts as both an application delivery mechanism and a drift detection/autohealing process. Operations via Pull Request GitOps isn’t just for developers;