allow developers to use familiar workflows, reducing the time it takes to spin up new development, test environments, or deploy new features to a cluster. Teams can ship more changes per day, and this based on values/variables. You can find more about them here. HELM FILE STRUCTURE test-chart Example ``` test-chart/ ├── charts #Required ├── Chart.yaml ├── NOTES.txt │ ├── serviceaccount.yaml │ ├── service.yaml │ └── tests │ └── test-connection.yaml └── values.yaml #Required ``` KUSTOMIZE Apart from the

to provision an environment The application behaves different in production than it did in test Environments are all manually configured (“pets vs. cattle”) Production deployments have Argo CD manage deployments? Approach 1: Multiple repositories /taxi-config-stage.git /taxi-config-test.git /taxi-config-prod.git /taxi-config-dev.git /taxi.git Approach 2 : Single Repository ├── apps required to manage SDLC 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

linear, basing each stage on previous ones. That’s why the term commonly used for the CI/CD build/test/deploy process is a pipeline. It can provide integration, delivery, and deployment in a continuous manifests are generally the same, and there are only slight differences between them in the dev and test environments. Now let’s do some customization. To render the YAML output for the dev environ- ment Branches Another best practice that surprises many programmers is to separate environments– such as test and production–into different directories, but not create branches for them. Like the separation

quality applications rapidly 2 Continuous Integration(CI) & Continuous Delivery (CD) 3 Build Test Security Checks Release Deploy Stage Deploy Prod Continuous Integration Continuous Delivery Monitor Detect drift Take action CD Continuous Integration & Continuous Delivery 10 Build Test Security Checks Release Deploy Stage Deploy Prod OpenShift Build Automate building container

Install into some cluster ● Tweak some simple configuration ● Add / remove offerings you are keen to test and see in action ● Add custom configuration on top of simple setup ● Install in cluster with Install into some cluster ● Tweak some simple configuration ● Add / remove offerings you are keen to test and see in action ● Add custom configuration on top of simple setup With requirements such as:

release pattern that allows you to release a new feature to a small percentage of users, let them test it out, and if it works well enough, make it available to everyone. It is a great way to enhance GitOps maturity. However, if your organization is at an early stage in this journey and you’d like to test the waters first, Weave GitOps Core is the underlying open source project that any organization can

Cloud 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

4 weeks 开发 Coding 上线 Online More Than 8 weeks 最终上线后，我需要维护… 运维复杂 Complex Ops 测试复杂 Complex Test 扩展复杂 Complex Scaling 稳定安全 Reliability, Security 只关注核心业务 核心业务逻辑 Core Business Code 数据库读写，文件存储

state) with what is currently running in the clusters. Build Deploy “Immutability Firewall” Test Operate & Manage IDE Monitor GIT GitOps unifies deployment, monitoring, and management GitOps

发布工程师 核心场景介绍：不同角色工程师基于统一协作平面，操作使用自动化工作流和云原生环境 面向角色 功能描述 工作流名称样例 具体配置 开发工程师 CI 过程 project-unit-test project-scan • 单元测试、代码扫描 更新日常开发环境及 dev 业务配 置 project-dev-workflow • 构建、配置变更（ Apollo/Nacos ）、数