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

Open Discussion on Project Planning Planning in an Agile Environment Key Tenets  Planning should focus strongly on the near term  Eliminate waste caused by planning for eventualities that never come Streamline processes to enable rapid and frequent delivery of capabilities Planning DOs and DON’Ts  DO establish some high-level planning, requirements, processes, and structure; however, activities focus concisely define the desired system functions and provide the foundation for Agile estimation and planning. o They describe what the users want to accomplish with the resulting system. User stories help

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

4About Me Other interests: Game engines Meta-programming 5Robot path planning 6Robot path planning Path planning 7Path planning How an (autonomous) agent figures out how to get from one location to level goals of this talk Implement cache-friendly path planning code in C++ 29High level goals of this talk Implement cache-friendly path planning code in C++ Do so using the STL 30High level goals of Implement cache-friendly path planning code in C++ Do so using the STL Try to keep our choices simple 31High level goals of this talk Implement cache-friendly path planning code in C++ Do so using the

simulation ○ Wheeled robots: navigation, localization, 3D perception ○ Robotic arms: control, motion planning ○ Tooling: logging, data visualization ● I love C++, and I learnt a lot thanks to CPPCon videos

involving users throughout development to ensure high operational value Agile practices integrate planning, design, development, and testing into an iterative lifecycle to deliver software at frequent intervals Structure and Processes for Agile Development ............................................. 15 7 Planning ............................................................................................... Figure 2 - Basic Agile Structure Enabling an Agile environment demands some degree of up-front planning and design, but the method emphasizes the importance of beginning development quickly. The fundamental

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

and abuse. I have so much fun working alongside you.” – Mark Schwartz Last Time in Part One Planning: The idea that we should make a plan and then stick to it is a terrible idea in an environment Agile fellows. In the past: We viewed EA as primarily concerned with standardization, consistency, planning, and cost reduction. It documented as-is and to-be architectures, demonstrated alignment of systems systems with business needs, and did the “rigorous” up-front analysis and centralized planning that could then be used to set boundaries for developers when they began a project. In other words, a vehicle

platform 02 03 04 Code reuse through libraries Building correct, secure, and safe systems Planning for the future Agenda Resources for learning modern C++ 0501 Obtaining tools for your platform platform 02 03 04 Code reuse through libraries Building correct, secure, and safe systems Planning for the future Agenda Resources for learning modern C++ 05Tools for your platform Build & platform 02 03 04 Code reuse through libraries Building correct, secure, and safe systems Planning for the future Agenda Resources for learning modern C++ 0501 Obtaining tools for your platform