背景 01 Horizon模板体系 02 GitOps最佳实践 03 Horizon产品介绍 04 Horizon落地 05 背景 第一部分 背景 云主机时代的痛点 2020年，云音乐开始容器化转型 效率 低下 计算 焦虑 运维 繁琐 成本 高昂 背景 业界优秀产品 站在巨人的肩膀上，打造符合公司中长期发展的 DevOps CD 产品 - Horizon Helm Chart的理念 Chart的理念 如何屏蔽 k8s 复杂性？ 屏蔽大部分细节，将少量配置开放给 使用者 集中了应用依赖的各种 资源 helm chart不足： • 面向开发者，对普通用户不友好 Horizon模板体系 第二部分 ├── Chart.yaml ├── README.md ├── schema ## 定义各种上层用户可理解的输入（支持前端自动渲染） └── status.sh └── values.yaml Horizon模板结构 模板组成： • Helm Chart • JsonSchema • ReactJsonSchemaForm (RJSF) 关注点分离： • 业务关注产品化 • 管理员关注底层实现 • 运维人员关注特殊场景的人工介入 Horizon模板最佳实践 管理员可以通过快速的配置，将一个复杂 应用的关键配置快速暴露给用户使用，保

负载均衡方面，支持 F5。  SDN 方面，支持华为 Agile Controller, VMware NSX-T, 华三 SDN。  物理机方面, 支持  DELL：R720，R730，R930  HP：DL 380 Gen8，DL 580 Gen8, DL 380 Gen9, DL 580 Gen8  IBM：IBM X3650M4  Inspur：5280M4，8480M4  容器云方面，支持

great way to enable an outstanding developer experience. GitOps is the best way to enable this platform approach. These two sentences are a concise summary of the key ideas in this paper. In the last way to foster an outstanding developer experience is to leverage the internal platform approach. An internal platform helps to get resources to developers on-demand and in a secure way. FAANG and startup teams to work with platform teams to improve overall organisational productivity and development velocity.” James Governor, — Source Redmonk.com Executive summary Adopting the platform approach alone

Directory Structures Repositories Reflecting an Organizational Boundary Kubernetes Platform Administrator Kubernetes Application Developer Other Boundaries GitOps Repo we struggled to adjust to life in a pandemic. Meeting customers one-by-one via the communication platform du jour wasn’t scalable. Our team started live streaming, and on October 9, 2020, Christian and groundbreaking technology that has created the newest versions of DevOps. The Kubernetes [1.5] container platform, in particular, has fostered a whole new way of thinking about application deployment, because

GitOps 是为云原生应用程序实施持续部署的一种声明方式。您可以使用 GitOps 创建可重复进程，用于在 多集群 Kubernetes 环境间管理 OpenShift Container Platform 集群和应用程序。GitOps 以快速的速度处 理和自动化复杂部署，节省部署和发行周期期间的时间。 GitOps 工作流通过开发、测试、临时和生产环境来推送应用程序。GitOps 部署新应用程序或更新现有应 OpenShift Container Platform 中，以及 Red Hat OpenShift Container Platform 的好处，以及 Red Hat Enterprise 支持、质量保证并专注于企业安全性。 注意 注意 因为 Red Hat OpenShift GitOps 的发行节奏与 OpenShift Container Platform 不同，所以 Red Hat OpenShift 可让您提供全局自定义资源，如用于配置 OpenShift Container Platform 集群的资源。 2.1. 主要特性 Red Hat OpenShift GitOps 可帮助您自动执行以下任务： 确保集群具有类似的配置、监控和存储状态 对多个 OpenShift Container Platform 集群应用或恢复配置更改 将模板配置与不同环境关联 在集群间（从调试到生产阶段）推广应用程序。

After a PR is merged, the changes are automatically applied using tools like Weave Kubernetes Platform. Once the system is described, it can be versioned in Git. All changes for operations and applications to accelerate and automate the installation of production-grade Kubernetes. The Weave Kubernetes Platform (WKP) works with Amazon Elastic Kubernetes Service (Amazon EKS). WKP includes enterprise-grade allowed us to create a self-service platform for engineers so they can concentrate on delivering business value through innovation, without the full need for Platform Team assistance. The engineers focus

the desired state, alongside purpose-built software agents (the backbone of the Weave Kubernetes Platform) and the automation already built into Kubernetes. But this increase in deployment velocity needn’t is improving developer productivity. By giving application developers access to a GitOps-based platform, they can use familiar tools and workflows (like pull requests) to optimize their efficiency. configurations, application configuration values and topology, while the operations team manages platform-wide configurations for policies, security and compliance, ensuring the guardrails are in place

infrastructure. Additionally, GitOps offers users the flexibility to select any tool, technology, or platform and use the same DevOps practices when creating infrastructure. Principles of GitOps There are repository. As GitOps is platform-agnostic, users can utilize any local or cloud-based Git repository such as: GitHub BitBucket Azure Repos GitLab Etc. Then comes the CI/CD pipeline platform, which boils down down to your preferred and familiar platform tools. Tools like Jenkins and CircleCI can be used with any git repository. BitBucket Pipeline and GitLab Pipelines prefer their own code repositories. Whatever

common in a large software team and unless you have a specialized tool on top of your deployment platform, it is very hard to answer them by only having access to a Git repository and its history. Running large organizations with multiple applications. Ideally, you would want a single deployment platform that follows the full journey of each code change, from commit to deployment. This way you will correlation between them, developers often have to build additional cruft on top of the deployment platform and ever resort to custom low-level scripts that tie them together. It is always important

com/brandonphillips/gitopsapp https://github.com/brandonphillips/rollout Codefresh Enterprise CI/CD platform for microservices Container-native Intuitive & Robust Enterprise Ready Flexible Delivery GitOps to sync MyApp source code 2. Trigger CI 3. Updates App manifest 4. Trigger CD pipeline CI/CD Platform 6. Get latest from repo Config Sync GitOps Demo! @codefresh ● Service Meshes: Istio, Linkerd source code 2. Trigger CI 3. Updates rollout manifest 4. Trigger canary CD pipeline CI/CD Platform Updated State Current State Updated State 5. Call ArgoCD to rollout and pause 7. Call ArgoCD