and Immutable Pulled Automatically Continuously Reconciled GitOps and CI/CD Traditional CI/CD Workflows Where does GitOps fit in? Operations via Pull Request Summary Infrastructure as Code Challenges of Infrastructure as Code Containers Change the Game Argo CD Flux Open Cluster Management Other GitOps Tools PipeCD Keptn Pulumi 33 Chapter 6–CI/CD with GitOps CI and CD Can Be Decoupled Integrating Synchronous and Asynchronous Tools CI Managed Benefits Drawbacks CI Owned and CD via GitOps

Contents The Principles of GitOps Key Benefits of GitOps What Happens When you Adopt GitOps? Typical CI/CD Pipeline GitOps Separation of Privileges 03 04 05 06 07 10 GitOps Hands On Tutorial Part Part 1: Spin up a Kubernetes Cluster Part 2: Fork the Sock Shop Repository Part 3: Setup CI and Connect a Container Registry Part 4: Let’s Get Started with GitOps Further Resources 11 works by using Git as a source of truth for declarative infrastructure and applications. Automated CI/CD pipelines roll out changes to your infrastructure when commits are pushed and approved in Git. It

OF DEVOPS Table of Contents 1. The Pains of GitOps 1.0 1.1. GitOps tools 1.2. Splitting CI and CD 1.3. Promotion of releases between environments 1.4. Modeling multi-environment configurations from features and not Git hashes 3.3. The new Codefresh GitOps dashboard 3.4. Argo CD Integration 3.5. CI/CD pipelines with Codefresh 3.6. Getting started with GitOps 2.0 Introduction points of GitOps: 1. GitOps covers only a subset of the software lifecycle 2. Splitting CI and CD with GitOps is not straightforward 3. GitOps doesn’t address promotion of releases between environments

Limiter la bande passante des images de disque . . . . . . . . . . . . . . . . . . 97 5.9 Support des CD/DVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 5.10 Serveurs iSCSI . . du serveur VBoxSVC out-of-process COM . . . . . . . . . . . 231 7 Contents 12.6.2 Changements de CD/DVD non reconnus . . . . . . . . . . . . . . . . . 232 12.6.3 Réponse lente en utilisant le client se charger . . . . . . . . . . . . . 233 12.7.2 Lecteur CD/DVD de l’hôte Linux non trouvé . . . . . . . . . . . . . . . 233 12.7.3 Lecteur CD/DVD non trouvé sur l’hôte Linux (distributions anciennes)

and systems needed to manage version control, configuration management, Infrastructure as Code, CI/CD, and observability have drastically increased. This puts an additional burden on the developer turnaround for new features and functionality for the customer. SELF-SERVICE With the existing CI/CD approach, the development team remains dependent on the operations team to deploy new changes in traditional CI-CD flow. We will also review core benefits over the traditional CI/CD approach. TRADITIONAL CI/CD WORKFLOW OVERVIEW Before diving further, let's first understand how traditional CI/CD works

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 11.18 Travis Ci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 11.21 Circle CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 the Conan client inside a conanfile . . . . . . . . . . . . . . . . . . . . 212 12.22 Use a generic CI with Conan and Artifactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 13 Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 12.18 Travis Ci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 12.21 Circle CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 the Conan client inside a conanfile . . . . . . . . . . . . . . . . . . . . 214 13.20 Use a generic CI with Conan and Artifactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 14 Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 11.18 Travis Ci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 11.21 Circle CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 the Conan client inside a conanfile . . . . . . . . . . . . . . . . . . . . 214 12.22 Use a generic CI with Conan and Artifactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 13 Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 12.18 Travis Ci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 12.21 Circle CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 the Conan client inside a conanfile . . . . . . . . . . . . . . . . . . . . 213 13.20 Use a generic CI with Conan and Artifactory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 14 Reference

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 11.18 Travis Ci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 11.21 Circle CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 they stay connected. Also, different clients building binaries from the same package recipe (like CI build slaves in different operating systems), will upload their binaries under the same package name