优化加速产研流程，工程师团队级规模化协 作，消除工具孤岛，系统性的提升人效 典型客户：字节飞书、云器、驭势、小鹏、 易快报、 MioTech 、星云有客、药师帮 大规模微服务环境治理 支持多分支、多业务间协作，消除环境不稳 定和不够用的阻力，高效率自动化验证质量 典型客户： TT 语音、飞书、钛动、闪电出 行 传统行业研发数字化转型 同步实现研发的数字化转型和 DevOps 不透明的测试环境导致大量问题 4. 为每一次部署维护一个 Chart 版本 现状 效能提升场景： 2K+ 微服务、多语言、 Helm 、 K8s 多集群 1. 开发流程 提交代码到 Feature 分支 -> GitLab-CI 自动构建打包 Chart （写一堆复杂 的脚本 ） -> -> Rancher 上手动替换 Helm Chart 版本 -> 调试 （使用 Chart -> Rancher 上手动替换 Helm Chart 版本 工具链： • GitLab （源码 + 服务 Chart 配 置） • Rancher 部署 分支策略： • feature -> develop/release -> master 环境策略： • 三套环境（ dev 、 qa 、 prod ） 现状：基于 GitLab + Helm

优化加速产研流程，工程师团队级规模化协 作，消除工具孤岛，系统性的提升人效 典型客户：字节飞书、云器、驭势、小鹏、 易快报、MioTech、星云有客、药师帮 大规模微服务环境治理 支持多分支、多业务间协作，消除环境不稳 定和不够用的阻力，高效率自动化验证质量 典型客户： TT语音、飞书、钛动、闪电出行 传统行业研发数字化转型 同步实现研发的数字化转型和DevOps落地 典型客 不透明的测试环境导致大量问题 4. 为每一次部署维护一个Chart 版本 现状 效能提升场景：2K+微服务、多语言、Helm、K8s 多集群 1. 开发流程 提交代码到 Feature 分支 -> GitLab-CI 自动构建打包 Chart （写一堆复杂的 脚本 ）-> -> Rancher 上手动替换 Helm Chart 版本 -> 调试（使用 kubectl/ 日志系统） GitLab-CI 自动构建打包 Chart -> Rancher 上手动替换 Helm Chart 版本 工具链： • GitLab （源码 + 服务 Chart 配置） • Rancher 部署 分支策略： • feature -> develop/release -> master 环境策略： • 三套环境（dev、qa、prod） 现状：基于 GitLab + Helm Chart

本地自测—— IDE 热部署 1. 查看服务和环境 2. 本地代码热部署到远端 测试验证 变更发布 需求开发 提交代码及 CI 过程 1. 本地编写代码推送到远端分支 1. 本地基于 develop 分支新建分支，在新建的分支上，编写代码 2. 推送代码到自己账号下的代码库 3. GitLab 上创建 MR 2. 自动触发 CI 过程，包括单元 测试，代码风格 检查、代码扫描

本地自测——IDE 热部署 1. 查看服务和环境 2. 本地代码热部署到远端 测试验证 变更发布 需求开发 提交代码及 CI 过程 1. 本地编写代码推送到远端分支 1. 本地基于 develop 分支新建分支，在新建的分支上，编写代码 2. 推送代码到自己账号下的代码库 3. GitLab 上创建 MR 2. 自动触发 CI 过程，包括单元 测试，代码风格 检查、代码扫描。

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 GitOps at scale 2.7 ArgoCD 3.1. Getting visibility into deployments 3.2. Deployment value 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 GitOps 2.0 Introduction GitOps is the practice of deploying applications by using Git Operations only (and not clicking UI buttons). The paradigm already existed in one form or another

Chapter 3–Templating Everything in Git Kustomize Helm Operators Combining Tools Summary The Path to GitOps | 3 Contents 22 Chapter 4–Git Workflows Separate Your Repositories infrastructure as code by keeping every- thing they wrote (including configurations) stored and versioned in Git, and by taking advantage of declarative configurations in Kubernetes. Cloud-Native DevOps So if The canonical example of the “versioned and immutable” principle is Git, which is why it’s the first element in the term GitOps. Git’s store is versioned and immutable because each change is tracked in

• Configuration Management in Kubernetes • GitOps for Kubernetes Essentials • Conclusion Git is the most widely used version control system, with more than 80 percent of its market share in today’s software industry. GitOps is a methodology which revolves around procedure and practices with Git at the center. It provides a fast and secure method for developers to maintain and update complex infrastructure and application configuration changes revolve around Git, i.e., the version control ecosystem. The focus is entirely on keeping Git as a single source of truth for infrastructure and application

by using Git as a source of truth for declarative infrastructure and applications. Automated CI/CD pipelines roll out changes to your infrastructure when commits are pushed and approved in Git. It also pieces together. Whatever you choose for your delivery pipeline, applying GitOps best practices with Git (or any version control) should be an integral component of your process. It will make building and of facts instead of by a set of instructions. With your application’s declarations versioned in Git, you have a single source of truth. Your apps can then be easily deployed and rolled back to and

building is Git. Git is widely used in software delivery, and its success is the reason why platforms like GitHub and GitLab are household names in every software delivery team today. Git has led to the GitOps - The way to build internal platforms GitOps views Git as the single source of truth. The entire system needs to be declared in Git and any changes are initiated using a simple pull request. GitOps allows you to create and manage your entire software stack through Git and treat your servers as your source code. Every change and configuration is done through a pull request and everyone

GitOps on AWS: Increase velocity of your DevOps teams P.2 Git familiar with DevOps and GitOps For over a decade, software companies have been trying to move away from the waterfall approach to application become experts in the orchestration tool. That’s where GitOps comes in. See how much faster you Git using DevOps and GitOps together Deployment/Cycle Time Deployment Frequency Change Lead Time between what is described in Git (the desired state) with what is currently running in the clusters. Build Deploy “Immutability Firewall” Test Operate & Manage IDE Monitor GIT GitOps unifies deployment