Considerations Multicluster Management Non-Declarative Infrastructure Security Base Image Selection Everything as Code Conclusion 45 About the Author The Path to GitOps | 5 Foreword deployment. If GitOps is just an extension of DevOps, then where does GitOps fit into the CI/CD workflow that has traditionally been the cornerstone of DevOps practitioners? I’ll try to answer that question integration, delivery, and deployment in a continuous stream of releases. Figure 1-1: The CI/CD workflow. Continuous integration builds and tests new code changes and merges them into a shared repository

dive into how GitOps workflow is different from our traditional CI-CD flow. We will also review core benefits over the traditional CI/CD approach. TRADITIONAL CI/CD WORKFLOW OVERVIEW Before diving a continuous integration tool kicks off unit tests that eventually build the Docker container image that gets pushed to the container registry. Figure 1 BROUGHT TO YOU IN PARTNERSHIP WITH REFCARD pipeline doesn't have its state easily recorded like when you're using GitOps. GITOPS DEPLOYMENT WORKFLOW OVERVIEW The GitOps core machinery is in its CI/CD tooling, with the critical piece being continuous

as code Git is the single source of truth Operations through Git workflows 5 GitOps Workflow a declarative approach to application delivery A A A What you want (desired state) What you Standard Workflow Multi-cluster consistency 7 Source Git Repository Image Registry CI The GitOps Application Delivery Model 8 Source Git Repository Config Git Repository Image Registry Application Delivery Model Pull Request Push Pull Push Pull Pull Request 9 Source Git Repository Image Registry CI The GitOps Application Delivery Model Config Git Repository Kubernetes Deploy

simple. Having everything in one place means that your operations team can also use the same workflow to make infrastructure changes by creating issues, and reviewing pull requests. GitOps allows code to Git, the continuous integration tool kicks off unit tests that eventually build the Docker image that gets pushed to the container registry. With a typical CI/CD pipeline, Docker images are Runs inside the production cluster Read/Write access to configuration repository Read access to image repository Read/Write access to the production cluster GitOps separates CI from CD and is a more

ArgoCD Managed Deployment Pipeline Managed Deployment Pro Consistent Post-Test update of image reference Con Image reference updated in git before integration tests, manage rollback? Inconsistent Con sync Application repo Environment repo Openshift Pipeline Updates image in dev manifest Push newly built container image Apply the newly updated manifests Infrastructure repo Application and Alibaba (announcement at KubeCon EU) ● Tekton and Argo CD as the basis of developer GitOps workflow 30 Dedicated GitOps View Empower developers with visibility of their application across all

should be managed. If they are stored in Git, they need to be encrypted and thus have their own workflow process during a deployment. If they are not stored in Git, then the whole idea of having your the latest Git commit matches again what is deployed in the cluster. Today to achieve this workflow, you need to write custom glue code in addition to adopting a GitOps tool. Running GitOps at the deployment was successful or not ● The pipeline(s) that were used for building the container image and deploying it ● The Kubernetes images that were affected ● The Kubernetes services/deployments

置 project-dev-workflow • 构建、配置变更（ Apollo/Nacos ）、数 据变更、部署、冒烟测试、项目管理任务 变更 测试工程师 更新测试验证环境 project-sit-workflow • 构建、配置变更（ Apollo/Nacos ）、数 据变更、部署、接口测试 更新集成测试环境 project-auto-sit-workflow • 构建，部署，场景测试 发布工程师 更新预发环境 project-uat-workflow • 质量门禁、构建、配置变更（ Apollo/ Nacos ）、数据变更、部署 uat （变量 变更、模板变更）、全量回归测试 更新生产环境 project-prod-workflow • 审批、配置变更（ Apollo/Nacos ）、数 据变更、部署生产环境（变量变更、模板 变更）、场景测试 管理员 ( 运维 ) 准备——工作

业务配置 project-dev-workflow • 构建、配置变更（Apollo/Nacos）、数据 变更、部署、冒烟测试、项目管理任务变 更 测试工程师 更新测试验证环境 project-sit-workflow • 构建、配置变更（Apollo/Nacos）、数据 变更、部署、接口测试 更新集成测试环境 project-auto-sit-workflow • 构建，部署，场景测试 发布工程师 发布工程师 更新预发环境 project-uat-workflow • 质量门禁、构建、配置变更 （Apollo/Nacos）、数据变更、部署 uat （变量变更、模板变更）、全量回归测试 更新生产环境 project-prod-workflow • 审批、配置变更（Apollo/Nacos）、数 据变更、部署生产环境（变量变更、模板 变更）、场景测试 管理员(运维)准备——工作流 管理员(运维)准备——工作流

pipeline to gain all the above benefits. In the next section, we’ll at how to implement a GitOps workflow properly. How to implement GitOps If your organization already has a properly implemented DevOps pipeline platform, its primary goal will be to: Automate the delivery process. Facilitate a clear workflow between the Git repository and the infrastructure management platform. (Learn how to build a CI/CD operators such as: Kubernetes Operator Terraform Cloud Operator Azure Service Operator Etc. GitOps workflow Now, we’ve got a Git repository and a properly configured CI/CD pipeline. An infrastructure engineer

IDE Monitor GIT GitOps unifies deployment, monitoring, and management GitOps is a standardized workflow for how to deploy, configure, monitor, update, and manage Kubernetes, it components, and all production environment matches the described state. P.4 Weave the principles of GitOps into everyday workflow The foundation of GitOps is based on the declarative nature of Kubernetes and its automatic deployment meets SOC 2 compliance just by using Git. Standardize workflows Establish an end-to-end CI/CD workflow driven by pull requests and fully reproducible through Git. Embed security Leverage Git’s correctness