3 KEY ELEMENTS FOR YOUR GITOPS STRATEGY Copyright 2024 Akamai Technologies. All rights reserved. Any trademarked names and logos are property of their respective companies. EBOOK GITOPS 3 KEY ELEMENTS . . . . . . . . . . . . . . . . . . . . . 12 | 03 3 KEY ELEMENTS FOR YOUR GITOPS STRATEGY Copyright 2024 Akamai Technologies. All rights reserved. Any observability is a critical part of GitOps and how it differs from monitoring Introduction | 04 3 KEY ELEMENTS FOR YOUR GITOPS STRATEGY Copyright 2024 Akamai Technologies. All rights reserved. Any

............................................................................... 22 杭州飞致云信息科技有限公司 3 6.1.3 Docker 查看................................................................................... 对象存储服务，支持常用私有云和公有云对象存储 漏洞扫描（scan） 绿盟漏洞扫描对接和漏洞分析 堡垒机（jumpserver） 用于 Jumpserver 堡垒机对接 AWS 费用管理（aws-billing-data） AWS 费用可视化分析、优化及分摊 物理机管理（physical-machine） 物理机自动发现及自助申请 负载均衡（loadbalancer-service） 负载均衡自服务及资源管理 firewall-cmd –reload 四、部署升级 4.1 部署环境说明 1) 端口检查（详见 #3.2 说明，确认是否开通相应的防火墙） 2) 服务器时间校准（服务需要和北京时间对时） 3) YUM 源配置 杭州飞致云信息科技有限公司 12 4.1.1 单机资源需求 项目 要求 CloudExplorer 系统及配置 CentOS/RHEL 7.6+ 64 位系统，8 核/16G

BUILDING & MANAGING INTERNAL PLATFORMS 3 weave.works ▼ Self-service developer experience (DX) In the past, the only way a developer could get access to servers, data, or software was to ask a system administrator built-in compliance Enforce zero-trust security Let’s look at each of these reasons in detail. 1 2 3 4 weave.works THE GITOPS GUIDE TO BUILDING & MANAGING INTERNAL PLATFORMS 6 ▼ ▼ As the infrastructure the evaluating product team discovered that they were able to operate their entire stack with only 3 developers. This instilled confidence in the team to move away from traditional architecture, and to

installment in the largest and longest-running project of its kind, pulling together six years of data drawn from over 31,000 technology professionals worldwide. It charts the performance of engineering deliver positive results in your organization. How GitOps Boosts Business Performance: The Facts 3 SOFTWARE SUCCESS LEADS TO OPERATIONAL SUCCESS In publishing its latest report, DORA has done more Businesses that are not performing well reported an average lead time of between one and six months. 3. Time to restore service This is defined by DORA as the average time from the detection of a user-impacting

Kubernetes Operator Summary 18 Chapter 3–Templating Everything in Git Kustomize Helm Operators Combining Tools Summary The Path to GitOps | 3 Contents 22 Chapter 4–Git Workflows brain-dump the details into meetings, documents, glossaries, and more. We built the GitOps Principles [3] based on knowledge and feedback from a wide swath of industry experts. We organized multiple workshops https://thenewstack.io/the-best-ci-cd-tool-for-kubernetes-doesnt-exist/ [2] https://youtu.be/UvwcVNv61Mo [3] https://opengitops.dev/#principles Foreword The Path to GitOps | 7 As Christian was writing this

delivering quality applications rapidly 2 Continuous Integration(CI) & Continuous Delivery (CD) 3 Build Test Security Checks Release Deploy Stage Deploy Prod Continuous Integration Continuous myapp-buildpack spec: source: url: https://github.com/myorg/myapp strategy: name: buildpacks-v3 builder: image: paketobuildpacks/builder:full output: image: quay.io/myorg/myapp:v1 kind: 0-jdk-8-slim command: [“mvn”] args: [“install”] - name: parse-yaml image: python3 script:|- #!/usr/bin/env python3 ... OPENSHIFT PIPELINES Tekton Concepts: Task 23 OPENSHIFT PIPELINES

rollbacks and secrets 2.6. Running GitOps at scale 2.7. Making the vision for GitOps 2.0 a reality 3. GitOps 2.0 with Codefresh & ArgoCD 3.1. Getting visibility into deployments 3.2. Deployment value 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 environments 4. There is no standard practice environment (more on this later) and you also introduce further manual steps just for release promotion. 3. “We only have one environment.” Great for small companies, but not feasible in other cases.

BROUGHT TO YOU IN PARTNERSHIP WITH REFCARD | GITOPS FOR KUBERNETES REFCARD | SEPTEMBER 2022 3 SINGLE SOURCE OF TRUTH In the GitOps world, version control systems (VCS) like Git should be the new feature is pushed to GitHub for review. 2. The code is reviewed and approved by a colleague. 3. After the code is revised and re-approved, it is merged to Git. 4. The Git merge triggers the CI pulls the changed manifests from the config repo, and deploys the new feature to production. Figure 3: GitOps workflow in Kubernetes GITOPS SECURITY The image is pulled using read-only access to the

Istio Multicluster First Demo About GitOps Second Demo What’s next? Control Plane Data Plane istiod Manages data plane components Handles Custom Resources Handles actual traffic Can be standalone Operator istio-operator Manages Istio installation with IstioOperator Custom Resource Example ● Data Plane with 5 proxies ● Each pod knows endpoint details of other pods ● Can be Sidecar or Gateway What to expect Istio Multicluster First Demo About GitOps Second Demo What’s next? Control Plane Data Plane istiod Some container Istio Sidecar Proxy Istio Ingress Gateway Istio Egress Gateway @rytswd

trails to identify details related to infrastructure changes such as Responsible users Deployment data time Affected resources Etc. The GitOps approach also helps to streamline the management of authentication Declare the infrastructure as code. 1. Push the code to a Git repository. 2. Create a pull request. 3. After that, this code can be reviewed and scrutinized by another team member and finally get approved—which