into a shared repository on a regular basis. CI is a form of rapid development that emerged as a result of the Agile Manifesto. CI is also a solution to the problem of having too many branches of an application grew in popularity, it helped drive the rise of the DevOps movement. Many new tools emerged as a result, including Chef, Ansible, Terraform, and CFEngine. One of the most popular tools was Puppet, which database to a fixed value can be issued multiple times safely. Doing so might be wasteful, but the result is the same each time, so the operation is idempo- tent. In contrast, adding a line to a log file

testing. Let’s say that you want to run some smoke tests AFTER a deployment has finished and the result of the tests will decide if a rollback will take place or not. Smoke tests As I said means that you are forced to use your CI solution again in order to run the smoke tests. The end result is a mixture of CI-CD-CI-CD components that goes against the main spirit of GitOps. There are also templates for Kubernetes manifests along with their runtime values that are merged to create the end result of what is deployed in the cluster. While you can provide a values.yml file on the fly when

declaratively. This declarative approach is focused on the result (desired state) rather than the steps needed to achieve the required result. This declarative approach allows users to specify the end

DevOps refinement, it’s become clear that the ops portion is the least understood by developers. As a result, many teams don’t realize the full benefits of their DevOps environment because the operational

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 guardrails and