GitOps Continuous Delivery with Argo and Codefresh BRANDON PHILLIPS | CODEFRESH Info slide (not for presentation) Original Abstract: GitOps is the gold standard for managing and deploying Kubernetes and organizational problems around CI/CD, Kubernetes application drift, and traceability through the engineering process. New: GitOps Continuous Delivery with Argo and Codefresh Description: Never make releases time and time again. Rather than pushing changes, Argo pulls and syncs code changes to a cluster. When combined with Codefresh’s CI/CD components we can get something magical. Brandon Phillips

triggered from Git Tools of the Trade https://argoproj.github.io/argo-cd https://kustomize.io/ Argo CD Kustomize Argo CD - What is It? Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes ○ Helm ○ Kustomize ○ Ksonnet/Jsonnet ○ Directories of yaml ● It is not a CI tool What is an Argo CD Application? apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: product-catalog-dev git targetRevision: master syncPolicy: automated: prune: false selfHeal: false ● Argo CD Application is a Custom Resource (CR) that defines the app in a declarative manner ● Application

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

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 comes 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

for delivering quality applications rapidly 2 Continuous Integration(CI) & Continuous Delivery (CD) 3 Build Test Security Checks Release Deploy Stage Deploy Prod Continuous Integration Continuous approach to application delivery A A A What you want (desired state) What you have (current state) CD Why GitOps? Reliably and consistently configure multiple Kubernetes clusters and deployment 6 Delivery Model 8 Source Git Repository Config Git Repository Image Registry Kubernetes CI CD The GitOps Application Delivery Model Pull Request Push Pull Push Pull Pull Request 9 Source

property of their respective owners. Abstract This document provides instructions for deleting the Argo CD instances added to the default namespace of the OpenShift GitOps Operator. It also discusses how . . . . Table of Contents CHAPTER 1. UNINSTALLING RED HAT OPENSHIFT GITOPS 1.1. DELETING THE ARGO CD INSTANCES 1.2. UNINSTALLING THE GITOPS OPERATOR 3 3 3 Table of Contents 1 Red Hat OpenShift GITOPS Uninstalling the Red Hat OpenShift GitOps Operator is a two-step process: 1. Delete the Argo CD instances that were added under the default namespace of the Red Hat OpenShift GitOps Operator.

is GitOps? ● Declarative cluster management ● All changes are driven by Git repo This demo uses Argo CD. Benefits are: ● Git repo becomes source of truth ● Clear change history ● Pull Request approval Demo What’s next? @rytswd NOTE: This demo is based on Istio Version 1.7.5. Argo CD https://github.com/argoproj/argo-cd Version v1.8.2 Grafana https://github.com/grafana/grafana Version v7.4.0, Helm

Alerting ※※※※ ※※※※※ ※※※※ Notification ※※※※ ※※※ ※※※※※ Application Template ※※※※ ※※※※※ ※※※※ CI/CD Pipeline ※※※※※ ※※※※※ ※※※ Application Lifecycle Management ※※※※※ ※ ※ Metering & Billing ※※※※※ Source-to-Image and Binary-to-Image supported Source-to-Image and Binary-to-Image not supported CI/CD Pipeline Jenkins pipelines supported with built-in graphical editing panels Jenkins pipelines visual editing panels (OpenShift Pipeline); GitOps supported with integration of built-in Argo CD and Tekton Jenkins pipelines supported with built-in graphical editing panels Code scanning

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

Application Catalog 4 4 3 1 Provision with Config Management Systems 4 3 3 3 Integration with CI/CD Solutions 3 4 2 4 Advanced Monitoring 4 4 3 2 Alerts and Notifications 4 4 3 2 External the environment. 3.3.3 CI/CD Capabilities • SUSE Rancher: 3 • OpenShift: 4 • Tanzu: 2 • Anthos: 4 3.3.3.1 SUSE Rancher SUSE Rancher integrates with any CI/CD system that works with Kubernetes already have a CI/CD system in place, they can leverage SUSE Rancher Continuous Delivery (SUSE Rancher CD) which incorporates the use of SUSE Rancher project Fleet. SUSE Rancher CD is a GitOps-based