GitOps on AWS: Increase velocity of your DevOps teams P.2 Git familiar with DevOps and GitOps For over a decade, software companies have been trying to move away from the waterfall approach to application wall to a separate engineering team and never seeing it again, they would prefer to have small teams of developers work together to handle everything themselves—from building and testing to deploying level. A new set of tools that can abstract the complexity of the steps previously handled by large teams must be adopted. The monolithic application should be split up into microservices that can each

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 translates into a faster turnaround for new features and GitOps empowers teams to become more efficient and strategic. It enables development teams to be more self-service in nature as they would be less dependent on platform and operations teams to deploy and what was desired. GitOps helps to measure and monitor what’s running on the cluster and notify teams if it`s desirable or undesirable. Every GitOps tool nowadays comes up with the ability to monitor

can be traced back to February 2001, when the Agile Manifesto [1.3] was published. In many ways, the Agile Manifesto is the grandfather of DevOps. Agile development practices were a big step toward improving application development process for the end user and for internal or external customers. However, while Agile focused on customer and developer experience, the process of delivering that software was still stuck up. The DevOps movement was born out of the need to automate application delivery. It allows the teams that wrote, delivered, and supported the software to work together in service of that goal. DevOps

associated infrastructure and applications through automation. GitOps is a natural evolution of Agile and DevOps methodologies What is GitOps? 3 Why GitOps? It takes weeks (or months!) to provision use-cases may work better with templates No support in OpenShift GUI console Great for enterprise teams, not as good for independent applications Kubernetes focused package manager based on templates

Automation 3. Code Review & Approve 4. Multi environment 5. CI/CD 6. Use Repository 7. Agile & Iteration DevOps 1. IaC 讓⼀切都成為 Code 2. Automation 盡可能⾃動化 如果不成，就紀錄它！ 3. Code Review & Approve 4. Multi environment 運⽤在所有的環境！ 5. CI/CD ⾃動化的唯⼀觸發點！ 6. Use Repository 分⽀策略、Flow、Workflow 7. Agile & Iteration ⼩粒度、多迭代 Tools VCS CI CD Container Registry CM IaC Container orchestration

TCE;  公有云方面，国内公有云支持阿里云、腾讯云、华为云，国外公有云支持 AWS、 Azure;  私有基础架构方面,  负载均衡方面，支持 F5。  SDN 方面，支持华为 Agile Controller, VMware NSX-T, 华三 SDN。  物理机方面, 支持  DELL：R720，R730，R930  HP：DL 380 Gen8，DL 580 Gen8

on-demand and in a secure way. FAANG and startup companies are increasingly building DX teams to work with platform teams to improve overall organisational productivity and development velocity.” James Governor build internal 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. consistent experience for your developers. Especially if your organization has numerous different teams, each with its own set of products, and priorities. A great developer experience gets out of the

an increase in innovation. This positive effect is not limited to the performance of engineering teams. Technology, in particular cloud native technology like Kubernetes and its ecosystem of projects drawn from over 31,000 technology professionals worldwide. It charts the performance of engineering teams across the world against four key measures: lead time for new features, failure rate of code changes 60%. How the best performing teams compare with the rest Across the organizations it studied, DORA identified huge differences in performance between the very best teams and their less successful counterparts

deployment and management of complex systems, improves collaboration between development and operations teams, and increases the reliability and reproducibility of deployments. GitOps is popular in the cloud-native allowing for better understanding and troubleshooting of complex and dynamic environments. This allows teams to monitor and troubleshoot issues more effectively. Additionally, since all changes are recorded compliance requirements can be easily met. Infrastructure as Code (IaC) One very common practice teams adopt for their GitOps strategy is implementing IaC tooling and best practices. The process involves

errors that can occur during deployments, saving time for Ops teams to diagnose and fix those errors. Besides, source control allows multiple teams to work on different parts of the infrastructure without interfering interfering with each other's work. This leads to increased productivity in both the Dev and Ops teams, which ultimately results in faster developments and deployments. Improved reliability & stability