Argo CD 搭配 Kustomize 實作 GitOps 部署 周育緯 1 About me •III DevOps contributor •8 年 System, DevOps 與 Backend 開發與 維護經驗 •資展國際、工研院: Kubernetes, DevOps 講師 2 GitOps •雲原生 Continuous Deployment •所有部署都使用聲明式(declarative)腳本 •需要維護5份yaml files •一份deployment yaml在用sed replace嗎? •容易出錯 •把他打包成Helm chart嗎？在帶入variable 嗎？ •複雜度過高 7 Kustomize •讓無模板的yaml可以支援多種用途 •CNCF special interest groups (SIGs) 贊助 •Kubernetes 1.14版開始支援 8 Sample Repoitory kustomization.yaml 15 用patch替換dev 使用的image tag 16 Kustomize Comand •kubectl kustomize {放置 kustomization.yaml 的資料夾名稱} •生成替換掉或增加參數的yaml •kubectl kustomize overlay/development 17 18 19 Use generate YAML

Pulumi Kubernetes Operator Summary 18 Chapter 3–Templating Everything in Git Kustomize Helm Operators Combining Tools Summary The Path to GitOps | 3 Contents 22 Chapter also work with Helm [2.2] and Kustomize [2.3] to render the YAML produced by those tools before applying them to the Kubernetes cluster. (We’ll look at Helm and Kustomize more closely in upcoming chapters GitOps Toolkit, and were based on controllers. These components include the source controller, the Kustomize controller, the Helm controller, the notification controller, and the image automation controller

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 state with git repos ● Works with a variety of Kubernetes deployment tools including: ○ Helm ○ Kustomize ○ Ksonnet/Jsonnet ○ Directories of yaml ● It is not a CI tool What is an Argo CD Application into it ○ Deploy required infrastructure before application (try to avoid this) ● Tools like kustomize and helm will handle this automatically in some cases ● Argo CD provides Sync Phases and Waves

yaml #Required ``` KUSTOMIZE Apart from the Parameterized Templating, another approach to manage is Overlay Configuration. Kustomize is a configuration management tool based based on this approach one. Kustomize works off a concept of “where, what, and how” to refactor specific Kubernetes manifests. The “where” to refactor/change are the base manifests, e.g., a deployment replica count, volume mounts, etc. The “how” to change are the kustomization/config files. Kustomize file structure example: ├── base │ ├── deployment.yaml │ ├── kustomization.yaml └── overlays

complex rollouts ● Rollback and rollforward to any Git commit ● Manifest templating support (Helm, Kustomize, etc) ● Visual insight into sync status and history OPENSHIFT GITOPS 29 An application scoped Configures webhooks for Tekton Pipelines for CI ● Configures Argo CD for deployment to environments ● Kustomize for environment-specific configs ● Integration with secret managers $ kam bootstrap $ kam environment

can and should focus on feature development @codefresh Practicing GitOps ● Templating: Helm, Kustomize, and more ● Configuration Drift: Monitors live state against desired state ● Enterprise Ready: