Challenges of Infrastructure as Code Containers Change the Game Argo CD Flux Open Cluster Management Other GitOps Tools PipeCD Keptn Pulumi Kubernetes Operator refined way to manage configurations and declare the state of everything in a given Kubernetes cluster called GitOps is something that Christian embraced wholeheartedly. Fast forward again to 2020, on a source of truth. Based on a reconciliation loop, the GitOps controller makes changes to the cluster by deploying new instances, once those changes have been committed to the state store. How a deployment

request Specifically for Kubernetes, GitOps says that you must not use `kubectl` to change the cluster state in an ad hoc manner. Instead, the desired state should be defined within GitOps tools at any on the deployment part of an application and nothing else. They solve the “I want to put in my cluster what is described in Git” problem, but all other aspects of software development are NOT covered: Git repository and takes care of the actual deployment by pulling changes in your cluster (and thus making the cluster state the same as the Git state). This scenario is great in theory and is certainly

of Privileges 03 04 05 06 07 10 GitOps Hands On Tutorial Part 1: Spin up a Kubernetes Cluster Part 2: Fork the Sock Shop Repository Part 3: Setup CI and Connect a Container Registry securely to complex applications running in Kubernetes. Freedom of choice Because there is no single tool that can do everything required in your pipeline, GitOps gives you the freedom to choose the Git, you have a single source of truth. Your apps can then be easily deployed and rolled back to and from Kubernetes. And even more importantly, when disaster strikes, your cluster’s infrastructure

revolve around Git, i.e., the version control ecosystem. The focus is entirely on keeping Git as a single source of truth for infrastructure and application configuration changes. In an ideal world, this deploy both application and infrastructure changes to Kubernetes. With the entire state of your cluster kept under source control, diff tools and synchronization agents can compare what’s running in two, an alert can be sent, effectively creating a feedback and control loop for managing your cluster. PRINCIPLES OF GITOPS GitOps is based on several core tenets: DECLARATIVE DESCRIPTION Thanks

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 other Multicluster First Demo About GitOps Second Demo What’s next? @rytswd Proof of Concept ● Install in cluster with other business applications, where there is some specific limitation, security requirements what business requires ● Break, debug, pinpoint, and fix Getting Started ● Install into some cluster ● Tweak some simple configuration ● Add / remove offerings you are keen to test and see in action

container cluster upwards are kept under source control. Any divergence from this desired state can be then observed and alerted on straight away. And if the worst happens, the entire cluster can be rolled teams to make crucial decisions before they deploy new features. Features or other updates like cluster configuration can be pushed to Git and then observed in real-time – and rolled back if necessary deployments both infrastructure changes and code, you automatically generate a full audit log of all cluster changes made outside of Kubernetes. In short, it tells you who did what, and when. These audit trails

with a team of developers who have to collaborate on a codebase to move it forward. Instead of a single developer who owns the codebase making all the decisions, a group of developers works together to software delivery called GitOps. GitOps - The way to build internal platforms GitOps views Git as the single source of truth. The entire system needs to be declared in Git and any changes are initiated using peers and automatically tested before it is deployed. Your platform should not be managed by one single person. It’s a bad idea to have one person who deploys code without anyone else knowing about it

and pull-requests” GitOps Benefits 5 GitOps is for Everyone Developers Operations Kubernetes Cluster Node 1 Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management applications OpenShift and GitOps - A Perfect Match ● OpenShift is a declarative environment ○ Cluster configuration is declared and Operators make it happen ○ Application deployments are declared and delivery tool for Kubernetes. ● Easily deploy applications in a declarative way ● Synchronizes cluster state with git repos ● Works with a variety of Kubernetes deployment tools including: ○ Helm

adopted. The monolithic application should be split up into microservices that can each be owned by a single team. Organizational leaders must also create a new culture that celebrates iterating and failing continuous deployment through the tools they work in everyday. Changes are automatically applied to the cluster once a Pull Request is approved and merged. Changes are handled by reconcilers that look for discrepancies the Git repo and reconcile any changes or divergences from inside the cluster. 1 3 2 4 GitOps doesn’t require cluster credentials or manual intervention to make a change to the system. As a

approach to Continuous Delivery and infrastructure operation Treat everything as code Git is the single source of truth Operations through Git workflows 5 GitOps Workflow a declarative approach Familiar tools and Git workflows from application development teams Standard Workflow Multi-cluster consistency 7 Source Git Repository Image Registry CI The GitOps Application Delivery Model Kubernetes-native on-demand delivery pipelines OpenShift GitOps Declarative GitOps for multi-cluster continuous delivery Ecosystem Integrations OpenShift GitOps 11 OpenShift Builds OpenShift