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

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

managing infrastructure as code is crucial. Essential elements of GitOps include continuous integration / continuous delivery (CI/CD), choosing between pull- or push-based architecture, and observability trademarked names and logos are property of their respective companies. As a base for exploring and planning your GitOps strategy, review the OpenGitOps Principles, published by the GitOps Working Group: in maintenance tasks. The dynamic and distributed nature of cloud-native applications requires continuous monitoring, updates, and security checks to ensure optimal performance and security. Push vs

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

contributor •8 年 System, DevOps 與 Backend 開發與 維護經驗 •資展國際、工研院: Kubernetes, DevOps 講師 2 GitOps •雲原生 Continuous Deployment •所有部署都使用聲明式(declarative)腳本 •所有部署環境yaml皆存放至Git repository 3 GitOps •所有對環境的調整，皆應由調整Git kubectl apply -f - 20 部署出dev deployment and service env 21 Argo CD 22 •A declarative, GitOps continuous delivery tool for Kubernetes 用ArgoCD 搭配kustomize來部署環境ㄌ 23 歡迎大家參考 III DevOps 更多詳細教學影音，請觀看我們的

Configuration GitOps = IaC + MRs + CI/CD Merge Requests GitOps = IaC + MRs + CI/CD Continuous Integration Continuous Delivery And Automation GitOps = IaC + MRs + CI/CD DevOps Photo by Fancycrave

https://kustomize.io/ Argo CD Kustomize Argo CD - What is It? Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. ● Easily deploy applications in a declarative way ● Synchronizes Argo CD on OpenShift Product Manager: Siamak Sadeghianfar ● Declarative GitOps operator for continuous delivery on Kubernetes ● Git as the single source of truth in sync with Kubernetes clusters