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 CI/CD platform for microservices Container-native Intuitive & Robust Enterprise Ready Flexible Delivery GitOps Objectives ● Repeatable - Apply changes the same way in every environment ○ Even your

*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

and executives have struggled for years to tailor the Defense Acquisition Framework to promote delivery of information technology (IT) capabilities in small, frequent releases – the approach that characterizes environment. “You never know less than on the day you begin your new project. Each incremental delivery / review cycle adds knowledge and provides insights that the team could have never known when developers, testing organization, acquirers, program management, and users is critical to Agile delivery. This demands a technically competent government team in addition to the development contactors

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 new, DevOps [1.1], or continuous integration/continuous deployment (CI/CD) [1.2]? As a matter of fact, GitOps unifies a collection of different topics in automation, application delivery, infrastructure management The process was speeding up, so the delivery of that software had to change to catch up. The DevOps movement was born out of the need to automate application delivery. It allows the teams that wrote, delivered

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 unifies your delivery pipeline, applying GitOps best practices with Git (or any version control) should be an integral component of your process. It will make building and adopting continuous delivery in your 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

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

now explore the key benefits GitOps brings to Kubernetes. INCREASED SPEED AND PRODUCTIVITY Continuous deployment automation with integrated feedback and control loops speeds up your deployment frequency understand how traditional CI/CD works as most organizations that set off on their journey to continuous delivery normally start by automating a CI/CD pipeline. In this simplified example, let's say there declare how the microservice runs in the cluster. When the developer pushes the code to Git, a continuous integration tool kicks off unit tests that eventually build the Docker container image that gets

Golang, Micro Service, Continuous Delivery and Docker 郭峰 联合创始⼈人@DaoCloud README.md # Development Challenge # Solution of Challenge: **Micro Service** # Challenge of Solution of Challenge # Solution needs 
 CI/CD Automation is Implicit Continuous Integration Continuous Integration to
 Continuous Diverse! Continuous Integration to
 Continuous Delivery “Works for me” “You need start A first” vagrant_wordpress_1 /entrypoint.sh apache2-for ... Up 0.0.0.0:80->80/tcp Reproducible Delivery The Landscape with Containers Demo Q&A