as measures of Software Delivery and Operational (SDO) performance and are metrics where elite and high performance excelled: 1. Deployment frequency DORA found that the world’s best performing businesses performance between the very best teams and their less successful counterparts. SDO Measure Elite High Medium Low Deployment frequency On-demand (multiple deploys per day) Between once per day deployment, but it also speeds up the detection and remediation of problems, which in turn boosts availability. This is achieved by using Git as the record for the desired state, alongside purpose-built

organized them by low, mid, and high DevOps maturity. The report highlighted a DevOps maturity model that shows 80% of organizations being ‘stuck in the middle’, yet to reach high levels of DevOps maturity teams. weave.works THE GITOPS GUIDE TO BUILDING & MANAGING INTERNAL PLATFORMS 4 ▼ Score for “high use” DevOps evolution Stream-aligned teams are essentially application development teams that build are many ways to deliver resources and tools to application developers, the favorite approach of high-performing DevOps teams is to deploy an internal platform that developers use to create and access

store. How a deployment is done will be described in later chapters. But I can describe it here at a high level. Under GitOps, the CI process just needs either to make a commit directly to your state store structures that require other considerations that are out of scope for this discussion. But taking a high-level look at things, two patterns arise when considering the structure of repositories: monorepo /functions_and_pipelines/ [5.3] https://argo-cd.readthedocs.io/en/stable/operator-manual/high_ availability/#monorepo-scaling-considerations [5.4] https://github.com/christianh814/example-kubernetes-go-repo

Benefits are: ● Separate cluster management for better control and audit ● Redundancy and High Availability But it does (did) pose challenges... What is Multicluster? Why? Target Audience What to expect

GitOps solution in place that not only cares about Git hashes but also offers full visibility on the high-level metrics of each deployment will allow all stakeholders to monitor the deployment process and multiple business features getting shipped. We need a way to present all this information in both high-level and low-level representations. On one hand, we need a way to provide a bird’s eye view of hashes, and deployments events that mean nothing to product owners or business analysts. 2. High-level “deployment” tools that are actually a fancy UI layer on top of a low-level tool exposing

you have to share your API credentials with the CI tooling. That means your CI tool becomes a high-value target. If someone breaks into your CI tool, they will have total control over your production

you have to share your API credentials with the CI tooling and that means your CI tool becomes a high value target. If someone breaks into your CI tool, they will have total control over your production