executing the CI/CD pipeline to provision or modify the infrastructure. Additionally, GitOps offers users the flexibility to select any tool, technology, or platform and use the same DevOps practices when declarative approach allows users to specify the end goal without worrying about each explicit step needed as in an imperative approach. As a state-aware declarative approach, users can easily store these states version-controlled approach, all the system infrastructure changes are available chronologically, enabling users to identify infrastructure changes over time easily. It is also helpful in: Troubleshooting Auditing

was looking for ways to extend it even further. In CustomResourceDefinitions (CRDs), Kubernetes users had a way to create all sorts of technology on Kubernetes clusters using familiar patterns. A more 6] package. Flux doesn’t render the YAML, but instead deals with Helm directly. This design gives users a familiar feel if they are already using Helm often. Originally, Flux was built as a monolithic components. Figure 3-2: Helm overview. Helm has a large ecosystem and many repositories that end users can draw on to de- ploy pre-built applications. If your organization uses Helm heavily, you’re in

important to first decide which deployment strategy fits well for your application and for your end users. Broadly, in GitOps, the below Kubernetes deployment strategies are well supported and can be reduces risk by slowly rolling out changes to an initially small subset of end users before rolling it out to all users. The canary deployment strategy ties together the best of both blue-green and

Application development teams Application development teams deliver applications and products to end-users. These teams are aligned according to the organization’s priorities. A common approach is for organizations is an advanced release pattern that allows you to release a new feature to a small percentage of users, let them test it out, and if it works well enough, make it available to everyone. It is a great

worth the effort. It allows developers to roll out changes and updates very quickly in response to users’ feedback without taking down the whole application and improves development metrics by orders of

Sign up for a Quay.io account, and record the user name. After you log in, you can see it under “Users and Organizations” on the top right of the repositories page. Create a new public repository called