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

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

gives that small team ways to speed up its inspecting and adapting process to maximize its impact. Continuous Delivery and DevOps place the entire value stream in the hands of that small team so that it can the current process, roles, responsibilities, and titles 4. Encourage leadership at all levels Planning Espousing the Wrong Values: The real reason we should reject the plan-driven approach to IT is when we substitute extensive planning for execution and when we substitute execution according to plan for thinking and adapting. A Better Way to Plan: Nevertheless, planning is important. In my role, I

Topic Nov 2015 Vote Tally Mike Ballou Agile Principles 0 Nick Tuck XP Prctices 1 Shawn Stumme Continuous Delivery 4 Josh Wade Cyber Security through Agile 2 Nick Tuck Maximizing Retrospectives 2 Ray Transparency 0 Ed Snodgrass Awesomeness through Stable Teams 0 Mike Ballou Open Discussion on Project Planning 1 Mike Ballou Contracting Agile Projects 0 Adam Raggett Agile Transparency 1 Nick Wenner Clean Version Control Comparison 1 Dr. Mark Roth Release It (Agile Book Review!) 1 Ray Page Release Planning 2 Darin Plum Agile Coaching 5 Nick Wenner Clean Coder (book review) 2 Josh Sagucio Collaborative

delivery often favored buying a product off the shelf. But when we view IT capabilities as being in a continuous state of transformation, when we see them as tightly integrated into an EA, and when we realize accomplish those objectives. When combined with Agile and Lean practices, this approach can focus IT planning, reduce risk, eliminate waste, and provide a supportive environment for teams engaged in creating to more accurately assess probabilities. Traditional teams attempt to drive out uncertainty by planning and analysis. Agile teams tend to drive out uncertainty by developing working software in small

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