platform approach alone is not enough. Organizations need to think strategically about how they would go about building and maintaining the platform. Further, how they would build a new development culture experience gets out of the way, leaving the developer in a flow state. DX allows developers to be more effective, by making the good thing the easy thing – in areas such as testing, security and observability reaching out to the cybersecurity people outside of their team. This bakes in security from the get-go and allows a security-first mindset even when developers are working on an MVP. Everything we do

Sumit 2020 From DevOps to GitOps with GitLab Cheng Wei Chen 陳 正瑋 DevOps Engineer @ 得寬科技
 《Effective DevOps 中⽂版》譯者、GitLab Hero http://chengweichen.com https://devopstw.club Agenda • 什麼是 GitOps

Path to GitOps, Christian decided to pursue a new role outside of Red Hat. While we’re sad to see him go, we’re also celebrating the opportunity he’s taken to continue to influence and evolve the GitOps automation, application delivery, infrastructure management, and security. In this chapter, I will go through each aspect of GitOps. By the end of the chapter, you will have a better under- standing of infrastructure man- agement after developer workflow, they aren’t identical. Later on in this book, we’ll go over how Git workflows for the infrastructure differ from the Git workflows from the application

everything is derived and driven. This trivializes rollbacks; where you can use a `Git revert` to go back to your previous application state. With Git’s excellent security guarantees, you can also use Container Registry eBook 25 3. Configure a Robot Account in Quay.io and then link it to Travis CI 1. Go back to Quay.io, select your repository. Create a Robot Account by selecting the + from the header token for the Quay robot account: Part 3: Setup CI and Connect a Container Registry eBook 27 4. Go back to TravisCI, and select the front-end repo. Select More Options → Settings. Toggle ‘Build pushed

feedback and control. But what is meant exactly by this? In order to have control so that developers can go faster, they need observability built into their deployment workflows. Built-in observability allows can be made against your running cluster before committing to that update. Or an update that didn't go as planned can be easily rolled back to a previously stable state. With a feedback control loop

Infrastructure as Code: Git is always the source of truth on what happens in the system ● Code changes always go through an automated process ● Deployments, tests, and rollbacks controlled through Git flow ●

和 o n l i n e 发 版 生 产 环 境 。 字节跳动 - 飞书场景一：主干开发主干发布 工具链： 飞书 + Gerrit + Zadig + 内部发布平台 技术栈： Go +git （ yml ） + 多集群 K8s 分支策略： 单分支 master 开发 环境策略： 4 套同构环境动态分配 测试管理： 500 API+E2E cases 字节跳动

环 境 和 o n l i n e 发 版 生 产 环 境 。 字节跳动 - 飞书场景一：主干开发主干发布 工具链： 飞书 + Gerrit + Zadig + 内部发布平台 技术栈： Go +git（yml）+多集群 K8s 分支策略： 单分支 master 开发 环境策略： 4 套同构环境动态分配 测试管理： 500 API+E2E cases 字节跳动 - 飞书场景二：

大幅降低资源部署变更环节的操作风险。 1.4.4 对于企业  改变研发与 IT 的协作模式，由“柜台式“协作转变为”ATM 在线服务“模式。  能够加速业务系统新功能开发测试投产上线，缩短新业务以及新功能 Go-To-Market 投 产周期。  能够释放大量人力，提升效率，降低成本。  能够减少资源的浪费，降低资源池建设和使用成本。 1.5 技术工具能力建设提升 1.5.1 建立 IT 在线服务自动化门户