single source of truth. It simplifies and standardizes the deployment and management of complex systems, improves collaboration between development and operations teams, and increases the reliability cloud-native architecture also brings about an increase in maintenance tasks. The dynamic and distributed nature of cloud-native applications requires continuous monitoring, updates, and security checks understand your deployment strategy, and be sure to empower your team with observability to keep your systems resilient and reliable. A GitOps approach complements the rapidity and flexibility of cloud-native

rightly so to improving the developer experience. In the last few years, the number of tools and systems needed to manage version control, configuration management, Infrastructure as Code, CI/CD, and declaratively via code. These declarative configurations will be stored ideally in your version control systems (VCS) like Git, GitLab, or GitHub. BROUGHT TO YOU IN PARTNERSHIP WITH REFCARD | GITOPS KUBERNETES REFCARD | SEPTEMBER 2022 3 SINGLE SOURCE OF TRUTH In the GitOps world, version control systems (VCS) like Git should be the only source of truth. Whatever changes one wants to perform in the

of Kubernetes knowledge, Christian would take the lead on building out some of the most complex systems our team could develop. Not only that, he saw a lot of potential for Kubernetes and was looking have changed the game for DevOps practi- tioners. The ways in which Kubernetes and cloud-native systems manage immutable instances (containers) have allowed DevOps practitioners to further refine their Working Group released the OpenGitOps Principles [1.10], a set of principles for managing software systems. We’ll look at the four major princi- ples in the sections that follow. Declarative The first OpenGitOps

transforming itself in recent years from a traditional organization with bureaucracy and legacy systems to one that is founded on open source software and modern cloud-native practices. Along the way their top priority. To make this transformation possible, they leveraged the platform approach to systems building. Security is baked into the platform at DoD so that developers only need to apply tags action can be replayed or rolled back at any time. Most of our teams operate their software and systems and are managing their infrastructure including Kubernetes clusters on their own. [The] GitOps approach

pipelines GENERAL DISTRIBUTION 17 What is Cloud-Native CI/CD? Designed with microservices and distributed teams in mind OPENSHIFT PIPELINES Containers Built for container apps and runs on Kubernetes

repository for all environments (or clusters) where all people collaborate along with the CI/CD systems. This creates the problem of Git conflicts (where your Git repos are touched by many CI processes features (i.e. issues from the ticket system such as JIRA) as they are typically handled by different systems. In order to create a correlation between them, developers often have to build additional cruft