Argo CD 搭配 Kustomize 實作 GitOps 部署 周育緯 1 About me •III DevOps contributor •8 年 System, DevOps 與 Backend 開發與 維護經驗 •資展國際、工研院: Kubernetes, DevOps 講師 2 GitOps •雲原生 Continuous Deployment •所有部署都使用聲明式(declarative)腳本 Repoitory •https://github.com/demoyuw/k8s-summit- cd-repository.git •Git clone https://github.com/demoyuw/k8s-summit- cd-repository.git •cd k8s-summit-cd-repository 9 10 kustomization.yaml 定義四個類別 •resources: kustomize overlay/development | kubectl apply -f - 20 部署出dev deployment and service env 21 Argo CD 22 •A declarative, GitOps continuous delivery tool for Kubernetes 用ArgoCD 搭配kustomize來部署環境ㄌ

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 and organizational problems around CI/CD, Kubernetes application drift, and traceability through the engineering process. New: GitOps Continuous Delivery with Argo and Codefresh Description: Never make releases time and time again. Rather than pushing changes, Argo pulls and syncs code changes to a cluster. When combined with Codefresh’s CI/CD components we can get something magical. Brandon Phillips

OpenShift Container Platform 4.13 CI/CD 包含有关 OpenShift Container Platform 构建、管道和 GitOps 的信息 Last Updated: 2024-02-17 OpenShift Container Platform 4.13 CI/CD 包含有关 OpenShift Container Platform 构建、管道和 other trademarks are the property of their respective owners. 摘要 摘要 OpenShift Container Platform 的 CI/CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 目 目录 录 第 第 1 章 章 OPENSHIFT CONTAINER PLATFORM CI/CD 概述 概述 1.1. OPENSHIFT 构建 1.2. OPENSHIFT PIPELINES 1.3. OPENSHIFT GITOPS 1.4. JENKINS 第 第 2 章 章 构

HorizonCD 云音乐在GitOps CD领域的最佳实践 朱旭 网易云音乐 云原生开发工程师 目 录 背景 01 Horizon模板体系 02 GitOps最佳实践 03 Horizon产品介绍 04 Horizon落地 05 背景 第一部分 背景 云主机时代的痛点 2020年，云音乐开始容器化转型 效率 低下 计算 焦虑 运维 繁琐 成本 高昂 背景 业界优秀产品 站在巨人的肩膀上，打造符合公司中长期发展的 DevOps CD 产品 - Horizon Helm Chart的理念 如何屏蔽 k8s 复杂性？ 屏蔽大部分细节，将少量配置开放给 使用者 集中了应用依赖的各种 资源 helm chart不足： • 面向开发者，对普通用户不友好 Horizon模板体系 第二部分 ├── Chart.yaml ├── README metadata: name: demo spec: replicas: 3 ... GitOps in Horizon Horizon作为面向用户的统一界面，用户不感知 gitlab 和 argo CD GitOps in Horizon 应用生命周期->代码库的生命周期 GitOps in Horizon GitOps in Horizon Horizon产品介绍 第四部分 Horizon介绍

第 1 章 章 什么是 什么是 GITOPS？ ？ 3 第 2 章 关于 RED HAT OPENSHIFT GITOPS Red Hat OpenShift GitOps 是一个使用 Argo CD 作为声明性 GitOps 引擎的 Operator。它启用了多集群 OpenShift 和 Kubernetes 基础架构的 GitOps 工作流。使用 Red Hat OpenShift GitOps，管理员可以在 GitOps，管理员可以在 集群和开发生命周期中一致地配置和部署基于 Kubernetes 的基础架构和应用程序。Red Hat OpenShift GitOps 基于开源项目 Argo CD，为上游提供的功能提供类似的功能，并提供额外的自动化功能，集成到 Red Hat OpenShift Container Platform 中，以及 Red Hat OpenShift Container Platform OpenShift GitOps 使用 Argo CD 来维护集群资源。Argo CD 是一个开源声明工具，用于应用程 序的持续部署(CD)。Red Hat OpenShift GitOps 将 Argo CD 实现作为一个控制器，以便持续监控 Git 存 储库中定义的应用程序定义和配置。然后，Argo CD 将这些配置的指定状态与集群中的实时状态进行比 较。 Argo CD 报告与指定状态不同的配置。报

triggered from Git Tools of the Trade https://argoproj.github.io/argo-cd https://kustomize.io/ Argo CD Kustomize Argo CD - What is It? Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes ○ Helm ○ Kustomize ○ Ksonnet/Jsonnet ○ Directories of yaml ● It is not a CI tool What is an Argo CD Application? apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: product-catalog-dev git targetRevision: master syncPolicy: automated: prune: false selfHeal: false ● Argo CD Application is a Custom Resource (CR) that defines the app in a declarative manner ● Application

Immutable Pulled Automatically Continuously Reconciled GitOps and CI/CD Traditional CI/CD Workflows Where does GitOps fit in? Operations via Pull Request Summary Infrastructure as Code Challenges of Infrastructure as Code Containers Change the Game Argo CD Flux Open Cluster Management Other GitOps Tools PipeCD Keptn Pulumi 33 Chapter 6–CI/CD with GitOps CI and CD Can Be Decoupled Integrating Synchronous and Asynchronous Tools CI Managed Benefits Drawbacks CI Owned and CD via GitOps

DEVOPS Table of Contents 1. The Pains of GitOps 1.0 1.1. GitOps tools 1.2. Splitting CI and CD 1.3. Promotion of releases between environments 1.4. Modeling multi-environment configurations comes from features and not Git hashes 3.3. The new Codefresh GitOps dashboard 3.4. Argo CD Integration 3.5. CI/CD pipelines with Codefresh 3.6. Getting started with GitOps 2.0 Introduction points of GitOps: 1. GitOps covers only a subset of the software lifecycle 2. Splitting CI and CD with GitOps is not straightforward 3. GitOps doesn’t address promotion of releases between environments

for delivering quality applications rapidly 2 Continuous Integration(CI) & Continuous Delivery (CD) 3 Build Test Security Checks Release Deploy Stage Deploy Prod Continuous Integration Continuous approach to application delivery A A A What you want (desired state) What you have (current state) CD Why GitOps? Reliably and consistently configure multiple Kubernetes clusters and deployment 6 Delivery Model 8 Source Git Repository Config Git Repository Image Registry Kubernetes CI CD The GitOps Application Delivery Model Pull Request Push Pull Push Pull Pull Request 9 Source

property of their respective owners. Abstract This document provides instructions for deleting the Argo CD instances added to the default namespace of the OpenShift GitOps Operator. It also discusses how . . . . Table of Contents CHAPTER 1. UNINSTALLING RED HAT OPENSHIFT GITOPS 1.1. DELETING THE ARGO CD INSTANCES 1.2. UNINSTALLING THE GITOPS OPERATOR 3 3 3 Table of Contents 1 Red Hat OpenShift GITOPS Uninstalling the Red Hat OpenShift GitOps Operator is a two-step process: 1. Delete the Argo CD instances that were added under the default namespace of the Red Hat OpenShift GitOps Operator.