and down based on CPU usage • Declarative in nature This list continues to grow with every release. Let’s now explore the key benefits GitOps brings to Kubernetes. INCREASED SPEED AND PRODUCTIVITY existing application and infrastructure configurations, making changes across them in different release cycles, and repeating BROUGHT TO YOU IN PARTNERSHIP WITH REFCARD | GITOPS FOR KUBERNETES ├── deployment.yaml │ ├── _helpers.tpl │ ├── hpa.yaml │ ├── ingress.yaml │ ├── NOTES.txt │ ├── serviceaccount.yaml │ ├── service.yaml │ └── tests │ └── test-connection

GitOps tools are sometimes marketed as the one-size-fits-all solution that will solve all your release problems and this is simply not true. First of all, GitOps requires that your deployment artifacts Classic pipeline With GitOps you can keep your CI process pristine (by just preparing a candidate release) and end it with a Git commit instead of a deployment. The Git commit is picked up by a deployment and your cluster for environment X is now getting the new version. But how do you promote this release to environment Y? Every time somebody declares that adopting GitOps is an easy process, I

pre-production environments. The changes can then, with the approval of the oper- ation teams or release managers, get deployed to production. This aspect of CD is an answer to the problem of poor visibility 5]. Argo CD was created to fill a need in the company’s infrastructure. Later, Intuit decided to release the Argo Project toolsets as open source. Since then, many companies, including Akuity, BlackRock parameters defined in the templates, and Helm injects these values into the manifests to create a release. A release is the end- Chapter 3 – Templating The Path to GitOps | 20 state representation of the YAML

platforms at scale. With these key strategic initiatives in place, software delivery teams can release software continuously, and with full confidence in the reliability of the system. THE GITOPS evolution Stream-aligned teams are essentially application development teams that build features and release code into production. Platform teams, on the other hand, exist to support application development where a corrupt configuration that made it to production did not even raise an alert because the release was so quickly rolled back. 2. Detect system and configuration drift Drift of any sort plagues

rapidly 2 Continuous Integration(CI) & Continuous Delivery (CD) 3 Build Test Security Checks Release Deploy Stage Deploy Prod Continuous Integration Continuous Delivery A key DevOps principle for Take action CD Continuous Integration & Continuous Delivery 10 Build Test Security Checks Release Deploy Stage Deploy Prod OpenShift Build Automate building container images using Kubernetes

staging ├── kustomization.yaml └── volumes.yaml ├── 00-tekton │ ├── release.notags.yaml │ └── release.yaml ├── 01-namespaces │ ├── cicd-environment.yaml │ ├── dev-environment.yaml │

Lead time for code changes This metric refers to the average time from check-in to production release. Businesses that perform best against this measure report average lead times of less than a day Performance: The Facts 4 4. Change failure rate This can be seen as a measure of quality in the release process. The best performers in the DORA study reported a change failure rate of less than 15%,

Cloud App Infra GitLab Runner 1. App 有更新嗎？ 2. infra 有更新嗎？ 3.有！執⾏異動！ Worker Build Test Release Validate Plan Validate Plan Approve 圖片來源 https://gitlab.com/gitops-demo/readme 圖片來源 https://gitlab

Chart 版本 工具链： • GitLab （源码 + 服务 Chart 配 置） • Rancher 部署 分支策略： • feature -> develop/release -> master 环境策略： • 三套环境（ dev 、 qa 、 prod ） 现状：基于 GitLab + Helm Chart 模版 + 多套 values

上手动替换 Helm Chart 版本 工具链： • GitLab （源码 + 服务 Chart 配置） • Rancher 部署 分支策略： • feature -> develop/release -> master 环境策略： • 三套环境（dev、qa、prod） 现状：基于 GitLab + Helm Chart 模版 + 多套 values 方 案 一 ： G e