1 Continuous Delivery and GitOps on OpenShift Christian Hernandez Technical Marketing Manager DevOps is the key to meet the insatiable demand for delivering quality applications rapidly 2 Continuous Continuous Integration(CI) & Continuous Delivery (CD) 3 Build Test Security Checks Release Deploy Stage Deploy Prod Continuous Integration Continuous Delivery A key DevOps principle for automation automation, consistency and reliability 4 What is GitOps? An developer-centric approach to Continuous Delivery and infrastructure operation Treat everything as code Git is the single source of truth

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 Kubernetes application drift, and traceability through the engineering process. New: GitOps Continuous Delivery with Argo and Codefresh Description: Never make a manual change again. In this talk we’ll Extensibility: Rich CLI, webhooks, events, and polished web UI @codefresh Argo CD A declarative GitOps continuous delivery tool for Kubernetes https://argoproj.github.io/argo-cd/ MyApp k8s manifest MyApp 1

*Tricentis 2021 Report: How The World's Top Organizations Test7 Aurora Innovation Agenda What is continuous regression testing How does regression testing work in practice How to build a regression testing Aurora Innovation Everything could go wrong “The inherent complexity of the real world and the continuous change of requirements result in large and complex software systems that are costly and dif�cult con�dence "Write tests. Not too many. Mostly integration." - Guillermo Rauch17 Aurora Innovation Continuous regression testing Continuously verifying that the software works as well as before, during the

recorded a podcast [1] to talk about tools in the Kubernetes space. Specifically, continuous integration (CI) and continuous delivery (CD) tooling. My mindset at the time was, “We can do better.” We had something you can buy off the shelf? Or is it just a fancy new term for DevOps [1.1], or continuous integration/continuous deployment (CI/CD) [1.2]? As a matter of fact, GitOps unifies a collection of different interval. “Continuous,” here, is understood in the industry to mean that reconciliation continues to happen at a chosen interval of time. Reconciliation doesn’t have to be instantaneous. Continuous reconciliation

GitOps is our name for how we use developer tooling to drive operations. GitOps is a way to do Continuous Delivery. More specifically, it is an operating model for building Cloud Native applications that control) should be an integral component of your process. It will make building and adopting continuous delivery in your organization easier and will significantly speed up your team’s ability to ship software agents act as the feedback and control loop for your operations. 1 3 2 4 eBook 5 Continuous deployment automation with an integrated feedback control loop speeds up your mean time to deployment

rollbacks 1.7. Observability 1.8. Auditing 1.9. Running at scale 1.10. GitOps and Helm 1.11. Continuous Deployment 1.12. Secrets management 2. A Vision of GitOps 2.0 2.1. Visibility into the Observability and business metrics 2.3. Promotion among different environments 2.4. Achieving Continuous deployment and full Git automation 2.5. Built-in handling for rollbacks and secrets 2.6. Running Running GitOps at scale is difficult 10. GitOps and Helm do not always work well together 11. Continuous Deployment and GitOps do not mix together 12. There is no standard practice for managing secrets

technical experts. End Users Conveys operational concepts and requirements/needs, participate in continuous testing activities, and provides feedback on developed capabilities. Enterprise Architect Creates development processes to fit the planned structure.16 While the Agile culture supports changes and continuous process improvement, the program should quickly establish a regular battle rhythm of time-boxed Magazine, “The Optimal Program Structure,” August 201218 7 Planning In an Agile environment, continuous planning occurs at every level – from the program to each release and sprint – and incorporates

(CI) What is Continuous Integration (CI)? • “The process of automating the build and testing of code every time a team member commits changes to version control” [What is Continuous Integration? - - Azure DevOps | Microsoft Docs]Continuous Integration (CI) What is Continuous Integration (CI)? • “The process of automating the build and testing of code every time a team member commits changes changes to version control” [What is Continuous Integration? - Azure DevOps | Microsoft Docs] What are the benefits? • Reduces risk – detect and locate errors more quickly • Ensures quality – shipped product

female X(s) = The hometown X(s) of a randomly drawn person (s) from (S) Examples: Continuous random variables (S is continuous) X(s) = r be the heart rate of a randomly drawn person s in our class S Feng valued random variable is a function of the outcome of a ran- domized experiment X : S → R For continuous random variable X P(a < X < b) = P({s ∈ S : a < X(s) < b}) For discrete random variable X P(X 9 / 122 Probability Distribution (Contd.) Probability distribution for continuous random variables Suppose X is a continuous random variable X : S → A Probability density function (PDF) of X is a

Respondents: 230 Continuous integration ... Continuous delivery wit... Continuous delivery wit... 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Answer Choices Responses Continuous integration for for build and test Continuous delivery with manual deployment to Production Continuous delivery with fully automated deployment to Production 11 / 37 2015 Jenkins Community Survey 20.69% 30 6.21% 9 9 20.00% 29 17.24% 25 18.62% 27 17.24% 25 Q12 If you are doing continuous delivery, how often do you make deployments to Production? Answered: 145 Skipped: 97 Total 145 Many times per day Once