time was, “We can do better.” We had new, declarative tools for infrastructure and a new paradigm to work. However, there weren’t many tools that had fully embraced Kubernetes natively. But a line in that GitOps [2]. It received very positive feedback and later became a recurring show. Eventually, this work led us to the Cloud Native Computing Foundation’s GitOps Working Group (and later the OpenGitOps concepts that seem unrelated. Is GitOps something that application developers use? Is it for infra- structure folks or system administrators? Is it something you can buy off the shelf? Or is it just a fancy

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 critical mission: to provide the resources and capabilities that enable application development teams to work effectively. A platform team delivers self-service APIs to developers. This team builds and maintains autonomy, but they also rely on the platform team to deliver the resources they need to get their work done. In this way, application development teams are internal customers of the platform team. In

Check Sync Status Synchronize Argo CD - Challenges It’s not all rainbows and unicorns ● Repo structure for manifests: ○ Monorepo; or ○ Separate repos for base/environments ● Managing secrets ● Order -objects/kustomization/#bases-and-overlays Kustomize is organized in a hierarchical directory structure of bases and overlays. ● A base is a directory with a kustomization.yaml file that contains a needless duplication of yaml ● Enables reuse through customization (patching) ● Hierarchical structure provides flexibility ○ Overlays can leverage other bases and overlays ○ Overlays can reference

all information in Git 9. Running GitOps at scale is difficult 10. GitOps and Helm do not always work well together 11. Continuous Deployment and GitOps do not mix together 12. There is no standard development strategy and you should make sure that all other processes and workflows are ready to work with GitOps. Splitting CI and CD with GitOps is not straightforward GitOps has been heralded well-known issues with GitOps and one of the first topics discussed when it comes to how GitOps can work in big organizations. Environment promotion The basic scenario for one environment is obvious

Kubernetes manifests based on values/variables. You can find more about them here. HELM FILE STRUCTURE test-chart Example ``` test-chart/ ├── charts #Required ├── Chart volume mounts, etc. The “how” to change are the kustomization/config files. Kustomize file structure example: ├── base │ ├── deployment.yaml │ ├── kustomization.yaml └── overlays ├──

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. The move to DevOps teams be more autonomous and productive by enabling continuous deployment through the tools they work in everyday. Changes are automatically applied to the cluster once a Pull Request is approved and

errors. Besides, source control allows multiple teams to work on different parts of the infrastructure without interfering with each other's work. This leads to increased productivity in both the Dev and

at the centre of the delivery pipeline, developers do not need to learn to use new tools. They can work in a world they know, using pull requests to accelerate deployment and operations tasks. The benefits the second of DORA’s SDO measures. Lead times are reduced with GitOps By enabling developers to work independently, GitOps makes them more productive, shortening lead times – defined by DORA as the

implementing a GitOps strategy. Repeatable processes and unified deployment methodologies allow teams to work asynchronously without sacrificing collaboration– this has become the key to bringing stable and

cluster Version 1 Version 2 Manage inbound and outbound traffic, allowing non-sidecar components to work with VirtualService setup #IstioCon Brush up on Istio resources (cont’d) Target Audience What