Kubernetes Operator Summary 18 Chapter 3–Templating Everything in Git Kustomize Helm Operators Combining Tools Summary The Path to GitOps | 3 Contents 22 Chapter 4–Git Argo CD can 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 that Flux uses the Helm Golang [2.6] package. Flux doesn’t render the YAML, but instead deals with Helm directly. This design gives users a familiar feel if they are already using Helm often. Originally

Zadig 企业交付案例场景深化 开 发 者 场 景 挖 掘 3-5 个领域敏感型场景 建立产品发展委员会 贡献者流程优化 2022 年 9 月 场 景 深 化 能 力 增 强 Helm/K8s YAML/ 托管场景接入流程优化 UX/UI 升级，工程师一线体验优化 推出效能看板，实时客观度量工程数据指标 效 率 优 化 、 开 发 者 体 验 增 强 2023 年 面向生态伙伴开放场景 为每一次部署维护一个 Chart 版本 现状 效能提升场景： 2K+ 微服务、多语言、 Helm 、 K8s 多集群 1. 开发流程 提交代码到 Feature 分支 -> GitLab-CI 自动构建打包 Chart （写一堆复杂 的脚本 ） -> -> Rancher 上手动替换 Helm Chart 版本 -> 调试 （使用 kubectl/ 日志系统） 自动构建打包 Chart （还是那堆复杂的脚 本） -> -> Rancher 上手动替换 Helm Chart 版本 -> 自动化 / 手工测试 3. 上线流程 合并 master -> GitLab-CI 自动构建打包 Chart -> Rancher 上手动替换 Helm Chart 版本 工具链： • GitLab （源码 + 服务 Chart

Zadig Zadig 企业交付案例场景深化 开 发 者 场 景 挖 掘 3-5 个领域敏感型场景 建立产品发展委员会 贡献者流程优化 2022年9月 场 景 深 化 能 力 增 强 Helm/K8s YAML/托管场景接入流程优化 UX/UI 升级，工程师一线体验优化 推出效能看板，实时客观度量工程数据指标 效 率 优 化 、 开 发 者 体 验 增 强 2023年 面向生态伙伴开放场景 不透明的测试环境导致大量问题 4. 为每一次部署维护一个Chart 版本 现状 效能提升场景：2K+微服务、多语言、Helm、K8s 多集群 1. 开发流程 提交代码到 Feature 分支 -> GitLab-CI 自动构建打包 Chart （写一堆复杂的 脚本 ）-> -> Rancher 上手动替换 Helm Chart 版本 -> 调试（使用 kubectl/ 日志系统） 2. 测试流程 合并到 GitLab-CI 自动构建打包 Chart （还是那堆复杂的脚本）- > -> Rancher 上手动替换 Helm Chart 版本 -> 自动化/手工测试 3. 上线流程 合并 master -> GitLab-CI 自动构建打包 Chart -> Rancher 上手动替换 Helm Chart 版本 工具链： • GitLab （源码 + 服务 Chart 配置） • Rancher

GitOps 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 problematic despite having all information in Git 9. 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. introducing performance issues when the repository is scanned for changes. GitOps and Helm do not always work well together Helm is the package manager for Kubernetes and is typically seen as the de-facto standard

cluster 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 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 to address repositories ● Included with kubernetes since 1.14 ● Validates yaml before deployment Kustomize vs Helm vs OpenShift Templates Patching framework Ability to apply yaml directly Some use-cases may work

management and packaging tools available. Let’s take a look at a few popular ones below: HELM Helm is based on the parameterized templating approach where all resource definition files of applications ecosystem. It acts just like APT/YUM/RPM packet manager but for Kubernetes. It runs on the concept of Helm Charts and Templates, which are shown below. When the Templates are combined with the values, these generate valid Kubernetes manifests based on values/variables. You can find more about them here. HELM FILE STRUCTURE test-chart Example ``` test-chart/ ├── charts #Required

成本 高昂 背景 业界优秀产品 站在巨人的肩膀上，打造符合公司中长期发展的 DevOps CD 产品 - Horizon Helm Chart的理念 如何屏蔽 k8s 复杂性？ 屏蔽大部分细节，将少量配置开放给 使用者 集中了应用依赖的各种 资源 helm chart不足： • 面向开发者，对普通用户不友好 Horizon模板体系 第二部分 ├── Chart.yaml ├── offline.sh │ ├── online.sh │ ├── startup.sh │ └── status.sh └── values.yaml Horizon模板结构 模板组成： • Helm Chart • JsonSchema • ReactJsonSchemaForm (RJSF) 关注点分离： • 业务关注产品化 • 管理员关注底层实现 • 运维人员关注特殊场景的人工介入

#IstioCon As of Feb 2021, with Istio v1.9, there are 5 mentioned in doc: ● istioctl ● IstioOperator ● Helm ● Multicluster ● Virtual Machine Istio installation patterns Target Audience What to expect Istio https://github.com/argoproj/argo-cd Version v1.8.2 Grafana https://github.com/grafana/grafana Version v7.4.0, Helm Chart Version v6.3.0 Prometheus https://github.com/prometheus/prometheus Prometheus Operator Version Multicluster Workshop by Denis Jannot & Christian Posta (Tuesday) ● Taming Istio Configuration with Helm by Ryan Michela (Wednesday) ● Know your peers by Alex Van Boxel (Wednesday) Target Audience What

deploying Kubernetes applications. In this talk, we’ll show you how we use raw Kubernetes, in addition to Helm and Terraform to manage our deployments to a wide range of clusters and clouds. Codefresh operates Developers can and should focus on feature development @codefresh Practicing GitOps ● Templating: Helm, Kustomize, and more ● Configuration Drift: Monitors live state against desired state ● Enterprise

解決辦法? •寫5份deployment 的yaml 嗎？ •需要維護5份yaml files •一份deployment yaml在用sed replace嗎? •容易出錯 •把他打包成Helm chart嗎？在帶入variable 嗎？ •複雜度過高 7 Kustomize •讓無模板的yaml可以支援多種用途 •CNCF special interest groups (SIGs)