# 云原生 DevOps 平台 ZADIG 产品介绍 ## 基本信息 ## 01 公司介绍 KodeRover 是国内云原生 DevOps 领域的领军企业，帮助企业提升产研工程化水平，加速产业数字化进程，快速响应市场需求。核心团队由国内外云计算、DevOps、工程运筹学领域专家组成，已连续完成由盈动和经纬领投的天使轮/PreA 轮融资。公司旗舰产品云原生 DevOps 平台 Zadig 正成 正成为软件研发的新标配，软件交付领域的规则制定者，开启了软件交付 3.0 时代。 ## 02 产品介绍 公司自主研发的旗舰产品 Zadig 在 GitHub 上核心开源，用平台工程支撑软件研发全生命周期，让产研高效协同，稳定迭代。Zadig 内置了 K8s YAML、Helm Chart、主机等复杂场景最佳实践，适用云原生转型/上容器云、研发效能提升、大规模微服务环境治理、研发数字化转型等应用场景 点的产品。我们充分感受到 Zadig 的优秀设计思想是非常值得字节 DevOps 团队借鉴学习的。”  ## Zadig 理念 & 应用 ## 一 体化平台帮助企业实现产研全域过程数据互通、软件质量透明、角色价值可评估 开发

## ZADIG：面向开发者的自助式云原生 DevOps 平台 协助产研团队实现云原生持续交付，帮助企业以更先进、更经济、更安全、更轻便的方式实现数字化研发转型  ## 为数千家企业所信赖 Revcbit inspur浪潮  ☐ 高人效 ☐ 低人效 高成人淹没在系统的海洋里：，无数平台手工切换 Zadig 云原生 DevOps 平台  Kubernetes 微服务 高人效 / 高质量 / 高效率 / 低成人在系统之外 / 上，复杂性下沉到单一平台 ## 产品发展历程 ## 基本能力开源

## ZADIG：面向开发者的自助式云原生 DevOps 平台 协助产研团队实现云原生持续交付，帮助企业以更先进、更经济、更安全、更轻便的方式实现数字化研发转型  ## 为数千家企业所信赖 Revcbit inspur 浪潮园  ☐ 高人效 ☐ 低人效 人淹没在系统的海洋里，无数平台手工切换 Zadig 云原生 DevOps 平台  Kubernetes 微服务 Zadig CI/CD 高人效/高质量/高效率/低成本： 人在系统之外/上，复杂性下沉到单一平台 ## 产品发展历程 ##

improvement blitz – dedicated and concentrated period of time to address a given issue b. Target DevOps Dojo and 30-Day Challenge – teams work with dedicated Dojo coaches and engineers, execute 2-day sprints other organizations & teams iv. Participate in peer reviews e. SHARE YOUR EXPERIENCES FROM DEVOPS CONFERENCES i. Cost is always a consideration. BUT, encourage attendance at conferences, give talks separation of duties #### 2. Ch. 22 – Information Security as Everyone’s Job, Every Day a. Many DevOps organizations have better results than when security is organized as a separate silo; fully integrate

The DevOps Handbook – Part 4: The Second Way – The Technical Practices of Feedback ### 1. Introduction a. Goal – Implement fast feedback loops i. Enable working towards shared goals ii. See problems without requiring time-sucking configuration changes or complicated processes.” iv. 2015 State of DevOps Report – high performers had MTTR 168x faster than low performers ### b. CREATE OUR CENTRALIZED Production System – “people closest to a problem typically know the most about it.” iii. 2014 State of DevOps Report – high performing organizations relied more on peer review and less on external approval of

The DevOps Handbook – Part 3 The First Way – The Technical Practices of Flow ### 1. Introduction a. Goal – Enable & sustain fast flow of work by implementing continuous delivery i. Create the foundation configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps Report – use of version control by Ops was the highest predictor of both IT performance & organizational created from trunk using a one-click process, and validated with automated tests.” v. 2015 State of DevOps Report – trunk-based development predicts higher throughput and better stability, and even higher

Myth—DevOps is Only for Startups: b. Myth—DevOps Replaces Agile c. Myth—DevOps is incompatible with ITIL d. Myth—DevOps is Incompatible with Information Security and Compliance: e. Myth—DevOps Means “NoOps” f. Myth—DevOps is Just “Infrastructure as Code” or Automation: g. Myth—DevOps is Only for Open Source Software: ### 2. Foreword xix 3. Imagine a World Where Dev and Ops Become DevOps: ### a. THE landscape 2. Provide stable, reliable, and secure service to the customer b. THE BUSINESS VALUE OF DEVOPS i. Code and change deployments (thirty times more frequent) ii. Code and change deployment lead

# DevOps A Horse’s Perspective # Just a horse, not a unicorn, 1000 deploys per/second not feasible. ## History - How I Got Here? ➢ Contentious relationship existed between development and operations code, Community of Practice, etc. ■ Test Driven Infrastructure Blue – green deployments Combining DevOps Scrum – planning, standups, boards, and backlogs ■ Making work visible (it’s still hidden) ■ Poor movements and changes ### “I’ll tell you EXACTLY what devops means.” Devops means giving a shit about your job enough to not pass the buck. Devops means giving a shit about your job enough to want to learn

## Kubernetes Native DevOps Practice - 王磊 @TenxCloud ## Agenda ## • Our DevOps Expectations ## • Kubernetes Capabilities/Advantages to Build DevOps Solution • Architecture and Features • CRD and operator Extensibility / Integration • CI/CD examples ## • Future plan ## Our DevOps Expectations • Build a platform and easy to integrate with other DevOps/third-party tools • Easy to be customized as user requirements Kubernetes Capabilities/Advantages to Build DevOps Solution • k8s itself is NOT a PaaS or DevOps platform, but ... • k8s resources that can be used to build DevOps solution Pod Job ![Image](/uploads/d

### GitOps 2.0 THE FUTURE OF DEVOPS ## Table of Contents 1. The Pains of GitOps 1.0 1.1. GitOps tools 1.2. Splitting CI and CD 1.3. Promotion of releases between environments 1.4. Modeling multi-environment way you will have full traceability on each production change and can also easily answer critical DevOps metrics such as lead time (the time it takes from a commit to reach production). ## Observability environment) is often missing or considered secondary knowledge. Additionally, some of the classic DevOps metrics are very hard to monitor with current GitOps tools. Especially the lead time (the time it