at Red Hat from the Ansible team to the OpenShift (Red Hat’s Kubernetes product) team. That was when I was introduced to Christian Hernandez. A font of Kubernetes knowledge, Christian would take the opportunity he’s taken to continue to influence and evolve the GitOps community. We’re excited to share Christian’s enthusiasm for GitOps here in his first book, and we’ll continue to support him and cheer 8 Chapter 1 What is GitOps? GitOps has quickly become the tech industry’s latest buzzword. Yet, when you search for GitOps, you will likely be presented with a lot of familiar concepts that seem unrelated

guide, we will describe several gaps and issues in current GitOps tools, and the biggest challenges when adopting GitOps workflows. Next, we will look at ideal scenarios, the features that tools should scenario is great in theory and is certainly applicable to simple scenarios, but it quickly breaks down when it comes to advanced deployments adopted by big organizations. The canonical example of mixing CI the main spirit of GitOps. There are also several underlying issues such as not knowing exactly when your environment has finished with the deployment in order to trigger the tests. The same scenario

is not in the technology itself, or the tools... The challenge is mainly building the structure inside the teams. We’re building many centers of excellences across all of our business units and all of exceptionally good at making components repeatable and reusable. This trait is especially useful when an application needs to be scaled at cloud burst speed. Being in the retail space, MediaMarktSaturn outside of their team. This bakes in security from the get-go and allows a security-first mindset even when developers are working on an MVP. Everything we do is based on Zero Trust architecture - both for

requirements, etc. ● Configure business applications to confirm it provides what business requires ● Break, debug, pinpoint, and fix ● Security ● Observability ● Supportability etc. #IstioCon Goal of requirements, etc. ● Configure business applications to confirm it provides what business requires ● Break, debug, pinpoint, and fix Getting Started ● Install into some cluster ● Tweak some simple configuration Many moving parts with the installation ● So much offering out of the box ● Even more complicated when there are multiple clusters Target Audience What to expect Istio Multicluster First Demo About GitOps

synchronization agents can compare what’s running in production with what’s under source control — and when a divergence is detected between the two, an alert can be sent, effectively creating a feedback systems. Containers took the world by storm and introduced new ways to orchestrate applications. When Google open-sourced Kubernetes in 2014, it grabbed the attention of developers and quickly became The way Kubernetes handles deployments lends itself very well to GitOps workflows. For example, when a group of configuration updates are made by a human operator, the Kubernetes orchestrator will

Freedom of Choice Table of Contents The Principles of GitOps Key Benefits of GitOps What Happens When you Adopt GitOps? Typical CI/CD Pipeline GitOps Separation of Privileges 03 04 05 06 07 infrastructure when commits are pushed and approved in Git. It also makes use of diff tools to compare the actual production state with what’s under source control and alerts you when there is a divergence apps can then be easily deployed and rolled back to and from Kubernetes. And even more importantly, when disaster strikes, your cluster’s infrastructure can also be dependably and quickly reproduced. ---------------

in some cases. However, developers using the DevOps approach can find the operations side tricky when they’re trying to spin up infrastructure on modern, cloud-native technologies. They need a way to Software agents continuously monitor 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

technology, or platform and use the same DevOps practices when creating infrastructure. Principles of GitOps There are a few core principles that apply when implementing and dealing with GitOps. Let’s take a is also helpful in: Troubleshooting Auditing Rollbacks Changes are automatically applied when approved When a pull or merge request is made, it will be verified and then approved since all the changes are stored in Git. Furthermore, it should be automated to apply changes to the system automatically when they are approved. GitOps prefers immediate automated deployments to achieve the desired state quickly

changes, GitOps provides a full audit trail. At any point, you can see exactly what changes were made, when and by whom. The key benefits of GitOps GitOps delivers much more than just increased velocity audit log of all cluster changes made outside of Kubernetes. In short, it tells you who did what, and when. These audit trails can be used to meet SOC 2 compliance, as well as making management easier. development pipeline. HOW GITOPS IMPROVES SDO PERFORMANCE DORA’s findings make it clear that when DevOps is implemented properly, both speed of development and stability of applications are improved

OpenShift 1 Jonas Janz AppDev Solutions Architect https://github.com/pixeljonas 2 GitOps is when the infrastructure and/or application state is fully represented by the contents of a git repository github-webhook-event-listener.yaml Argo CD - Managing Secrets How do I store Kubernetes secrets securely in git when a secret is not encrypted and is only base64? ● Externalize the secret using products like Vault