and Immutable Pulled Automatically Continuously Reconciled GitOps and CI/CD Traditional CI/CD Workflows Where does GitOps fit in? Operations via Pull Request Summary Conclusion 33 Chapter 6–CI/CD with GitOps CI and CD Can Be Decoupled Integrating Synchronous and Asynchronous Tools CI Managed Benefits Drawbacks CI Owned and CD via GitOps GitOps Benefits Drawbacks CI Triggered and GitOps Owned Benefits Drawbacks A Mindset Shift Conclusion The Path to GitOps | 4 Contents 37 Chapter 7–Handling Secrets

deployment tools including: ○ Helm ○ Kustomize ○ Ksonnet/Jsonnet ○ Directories of yaml ● It is not a CI tool What is an Argo CD Application? apiVersion: argoproj.io/v1alpha1 kind: Application metadata: dependent deployments ● Non-declarative requirements ● Integrating with CI/CD tools (Jenkins, OpenShift Pipelines, etc) ○ Does CI/CD or Argo CD manage deployments? Approach 1: Multiple repositories ├── dev-ci-build-from-pr-binding.yaml │ ├── dev-ci-build-from-pr-template.yaml │ ├── stage-cd-deploy-from-push-binding.yaml │ ├── stage-cd-deploy-from-push-template.yaml │ ├── stage-ci-dryrun-from-pr-binding

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 configurations features and not Git hashes 3.3. The new Codefresh GitOps dashboard 3.4. Argo CD Integration 3.5. CI/CD pipelines with Codefresh 3.6. Getting started with GitOps 2.0 Introduction GitOps is pain points of GitOps: 1. GitOps covers only a subset of the software lifecycle 2. Splitting CI and CD with GitOps is not straightforward 3. GitOps doesn’t address promotion of releases between

meet the insatiable demand for delivering quality applications rapidly 2 Continuous Integration(CI) & Continuous Delivery (CD) 3 Build Test Security Checks Release Deploy Stage Deploy Prod Continuous Source Git Repository Image Registry CI The GitOps Application Delivery Model 8 Source Git Repository Config Git Repository Image Registry Kubernetes CI CD The GitOps 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 Monitor Detect

code is crucial. Essential elements of GitOps include continuous integration / continuous delivery (CI/CD), choosing between pull- or push-based architecture, and observability. Getting Started with GitOps to the automation of infrastructure. This includes version control, collaboration, compliance, and CI/CD. GitOps is a specific implementation of DevOps that uses Git as the single source of truth for trigger processes with your CI/CD tooling to update the config repo. The config changes are then pushed/pulled to the deployment environment. Git Repo 1 Git Repo 2 CI/CD Infrastructure as Code

these tools and resources that eliminate obstacles. Developers should not have to file a list of support tickets and wait forever to get what they need. It’s a good idea to have a consistent process in that build features and release code into production. Platform teams, on the other hand, exist to support application development teams and make resources available to them whenever needed. Application The platform they build is a collection of self-service APIs, tools, services, knowledge, and support. Development teams have a high degree of autonomy, but they also rely on the platform team to

one month Change failure rate 0-15% 0-15% 0-15% 46-60% A surprise: speed and stability support one another Combining the first and second SDO measures (lead time and deployment frequency) provides infrastructure, your apps and Kubernetes itself, right across your organization. Not only will all your CI/CD pipelines be driven by pull request, but operations tasks will also be fully reproducible through

求参数方式。这个在开发团队规模较大，申请虚拟机数量比较多的企业中非常有用，比如银 行。 5）服务目录产品支持单机、批量多机、以及中间件数据库集群部署、由多个虚拟机组 成的运行环境部署等。在管理侧还可以按需提供 CI CD 工具、运维工具等产品供选择部署 使用。可向管理员提申请要求。 杭州飞致云信息科技有限公司 软件用起来才有价值，才有改进的机会 21 图 14: 方便快速申请一批虚拟机 服务目录支持各类指定版本的软件部署产品。 CentOS/RHEL 7.4+ 干净的系统 VIP 2 N/A N/A 八、详细功能列表参数 详细功能列表参数请见<>，请联系公司 销售邮箱: support@fit2cloud.com 如果是合作伙伴，报备项目请登陆公司官网，右上角点击【合作伙伴项目报备】报备项 目。 公司官方网站: www.fit2cloud.com

Contents The Principles of GitOps Key Benefits of GitOps What Happens When you Adopt GitOps? Typical CI/CD Pipeline GitOps Separation of Privileges 03 04 05 06 07 10 GitOps Hands On Tutorial Part 1: Spin up a Kubernetes Cluster Part 2: Fork the Sock Shop Repository Part 3: Setup CI and Connect a Container Registry Part 4: Let’s Get Started with GitOps Further Resources 11 works by using Git as a source of truth for declarative infrastructure and applications. Automated CI/CD pipelines roll out changes to your infrastructure when commits are pushed and approved in Git.

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 turnaround for new features and functionality for the customer. SELF-SERVICE With the existing CI/CD approach, the development team remains dependent on the operations team to deploy new changes traditional CI-CD flow. We will also review core benefits over the traditional CI/CD approach. TRADITIONAL CI/CD WORKFLOW OVERVIEW Before diving further, let's first understand how traditional CI/CD works