. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 05 Push vs . Pull-Based Architecture . . . . . . . . . . . . . . . . . . cloud-native ecosystem, particularly in Kubernetes-based environments, where managing infrastructure as code is crucial. Knowing the philosophy of GitOps, what your current deployment strategy looks like, cloud-native ecosystem, particularly in Kubernetes-based environments, where managing infrastructure as code is crucial. Essential elements of GitOps include continuous integration / continuous delivery (CI/CD)

different in production than it did in test Environments are all manually configured (“pets vs. cattle”) Production deployments have a very low success rate I have no visibility or record are easily stored and managed in git OpenShift GitOps Principles ● Separate application source code (Java/.Net/etc) from manifests (yaml) ● Deployment manifests are standard k8s manifests ● Avoid 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

Serverless、Serverless 提供的运维能力 Serverless 业务运维能力 & 系统运维能力 Serverless 和 虚拟机 2 种形态下运维能力对比 Serverless vs. IaaS 运维能力对比 Serverless 和 虚拟机 2 种形态下运维能力对比 Serverless 运维案例 腾讯相册微信小程序运维案例 目录 Serverless 介绍 2014 (Backend as a Service) Serverless ≈ CaaS + BaaS 用户运维 Serverless 介绍 Physical Machine vs. Virtaul Machine vs. Container vs. Serverless Hardware Virtualization O/S Containers Runtime Applications Functions Timer 调用 函数代码 依赖 本地 开发者 Serverless 介绍 Serverless 业务运维能力 业务运维能力 DevOps 开箱即用 工具建设 工具 ❑ VS Code IDE 插件 ❑ WebIDE ❑ Command Line 功能 ❑ 函数增删改查 ❑ 调试 ❑ 打包部署 ❑ 日志 ❑ … DevOps 解决方案 Coding DevOps Serverless

application. It utilizes Git as the source code management tool for managing the infrastructure code. In other words, GitOps is an evaluation of infrastructure as code and DevOps practices which uses Git as application infrastructure GitOps allows developers or the Ops team to declare their infrastructure as code and version control them via Git. Whenever a new change is required, a pull request with the new change undergo almost the same verification and validation process for application code with consistent: End-to-end workflows Standardized code structures Documentation Testing methods This introduces standardized

tools and systems needed to manage version control, configuration management, Infrastructure as Code, CI/CD, and observability have drastically increased. This puts an additional burden on the developer of the application. Ideally, the developer focuses mainly on delivering business value via code. Thus, to improve developer experience, GitOps emerged where infrastructure and application configuration configuration changes. In an ideal world, this approach allows the developer to focus on working and pushing code to Git, and then, further deployment and tweaks would be taken care of by an automated mechanism

DevOps 方案对比 来自客户的评价： 2 Zadig 产品特性 Zadig 核心特性 面向开发者的云原生环境 灵活易用的高并发工作流 高效协同的测试管理 云原生 IDE 插件（ VS CODE) 客观精准的效能洞察 强大免运维的模版库 • 自动生成面向开发、测试、运维角 色的工作流 • 多个微服务并行构建、部署、测 试，代码验证效率 UP • 自定义工作流，灵活编排发布、自 高开发效率 可重用降低运维成本 • 一些组织可能过度依赖高级工程 师管理发布流程和基础设施，导 致资源浪费和效率低下 Zadig 平台工程模式 工程规模数据： • 1500+ 产研工程师 Vs. 2 人运维 • 50 + 个 Kubernetes 全球集群 • 300+ 个数字产品（资产沉淀） • 1600+ 条自动化工作流（全域） • 900+ 个服务化运行环境 通过整

与现存 DevOps 方案对比 来自客户的评价： Zadig 产品特性 Zadig 核心特性 面向开发者的云原生环境 灵活易用的高并发工作流 高效协同的测试管理 云原生 IDE 插件（VS CODE) 客观精准的效能洞察 强大免运维的模版库 • 自动生成面向开发、测试、运维角 色的工作流 • 多个微服务并行构建、部署、测试， 代码验证效率 UP • 自定义工作流，灵活编排发布、自 高开发效率 可重用降低运维成本 • 一些组织可能过度依赖高级工程 师管理发布流程和基础设施，导 致资源浪费和效率低下 Zadig 平台工程模式 工程规模数据： • 1500+ 产研工程师 Vs. 2 人运维 • 50 + 个 Kubernetes 全球集群 • 300+ 个数字产品（资产沉淀） • 1600+ 条自动化工作流（全域） • 900+ 个服务化运行环境 通过整合业务

developer-centric approach to Continuous Delivery and infrastructure operation Treat everything as code Git is the single source of truth Operations through Git workflows 5 GitOps Workflow a your own build tools ● Based on Shipwright open-source project OpenShift Builds 14 Application code Runtime image Build tools image Runtime image OpenShift Builds Application image GENERAL Pipeline templates when importing apps ● Automated install and upgrades via OperatorHub ● CLI, Web, VS Code and IntelliJ plugins OPENSHIFT PIPELINES 21 Task step step Task step Task step step Task

from the waterfall approach to application development to the DevOps approach. Instead of throwing code over a wall to a separate engineering team and never seeing it again, they would prefer to have small together Deployment/Cycle Time Deployment Frequency Change Lead Time Change Failure Rate MTTR vs. MTTF (mean time to recover/fail) P.3 Simplify Kubernetes operations using developer tools GitOps is just one example of many modern, cloud-native tools that are declarative and can be treated as code. The system’s entire infrastructure must be described in Git. After a PR is merged, the changes

负载均衡配置在线申请及变更删除............................................................................ 72 7.1 申请 F5 负载均衡 VS 实例............................................................................... 72 7.2 查看 F5 订单信息及状态 ............................................................................... 73 7.3 查看 F5 负载均衡 VS 实例................................................................................ 73 7.4 添加负载后端服务器 ................................................................................75 7.7 回收 F5 负载均衡 VS 实例................................................................................ 75 8 云数据库在线申请部署及操作变更回收