Kubernetes and containers Cloud-Native DevOps A DevOps Operating Model GitOps Principles Declarative Versioned and Immutable Pulled Automatically Continuously References Conclusion 41 Chapter 8–Other Considerations Multicluster Management Non-Declarative Infrastructure Security Base Image Selection Everything as Code Conclusion continuous delivery (CD) tooling. My mindset at the 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

Git is the single source of truth Operations through Git workflows 5 GitOps Workflow a declarative approach to application delivery A A A What you want (desired state) What you have (current The GitOps Application Delivery Model 8 Source Git Repository Config Git Repository Image Registry Kubernetes CI CD The GitOps Application Delivery Model Pull Request Push Pull Push Pull Pull Request 9 Source Git Repository Image Registry CI The GitOps Application Delivery Model Config Git Repository Kubernetes Deploy Monitor Detect drift Take action CD Continuous

and 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 services on-premise, across multiple sites, clouds, and at the edge with the standard GitOps operating model. Our application teams have more or less all the basics in their hands to start deploying and running as bad actors cannot easily hide their actions from the sidecar. The first benefit of a sidecar model is, because it is injected alongside and not inside a container, you can independently update the

automated mechanism. Since Kubernetes and many other cloud-native technologies are almost entirely declarative, infrastructure definitions can be kept alongside application code in Git. Keeping your entire for managing your cluster. PRINCIPLES OF GITOPS GitOps is based on several core tenets: DECLARATIVE DESCRIPTION Thanks to modern Infrastructure as Code (IaC) and configuration management tools you can define, configure, and spin up your entire application declaratively via code. These declarative configurations will be stored ideally in your version control systems (VCS) like Git, GitLab

implementing and dealing with GitOps. Let’s take a look. Declarative system In the GitOps model, the complete system is configured declaratively. This declarative approach is focused on the result (desired state) required result. This declarative approach allows users to specify the end goal without worrying about each explicit step needed as in an imperative approach. As a state-aware declarative approach, users can facilitating convenient deployments and rollbacks. The system state is versioned in Git All the declarative states are stored in the version-controlled system, which acts as the single source of truth. With

specifically, it is an operating model for building Cloud Native applications that unifies Deployment, Monitoring and Management. It works by using Git as a source of truth for declarative infrastructure and applications Kubernetes is just one example of many modern cloud native tools that are “declarative” and that can be treated as code. Declarative means that configuration is guaranteed by a set of facts instead of by 4. Higher Reliability 5. Increased Consistency and Standardization Because GitOps provides one model for making infrastructure, apps and add on changes, you have consistent end to end workflows across

Business Performance: The Facts 5 WHAT IS GITOPS? GitOps is a set of best practices and an operational model that reduces the complexity of Kubernetes and makes it easier to deliver on the promise of DevOps and its ecosystem of cloud native tools are declarative, as opposed to imperative, which allows for configuration to be treated as code. It is this declarative nature that enables the infrastructure to The Facts 7 5. Consistent workflows GitOps has the potential to provide a single, standardized model for amending your infrastructure, your apps and Kubernetes itself, right across your organization

it components, and all the applications that run on it. In GitOps, a Git repository contains declarative descriptions of all desired elements in the production environment while an automated process Weave the principles of GitOps into everyday workflow The foundation of GitOps is based on the declarative nature of Kubernetes and its automatic deployment of committed files. GitOps leverages these attributes following principles: Kubernetes is just one example of many modern, cloud-native tools that are declarative and can be treated as code. The system’s entire infrastructure must be described in Git. After

GitOps is a specific implementation of DevOps that uses Git as the single source of truth for declarative infrastructure and application code. In GitOps, the desired state of the system is versioned published by the GitOps Working Group: The desired state of a GitOps managed system must be: 1. Declarative A system managed by GitOps must have its desired state expressed declaratively. a successful transition. The first hurdle is modifying your application to fit the cloud-native model. This process involves re-architecting applications fit into a standardized and vendor-agnostic workflow

platform, services, and applications OpenShift and GitOps - A Perfect Match ● OpenShift is a declarative environment ○ Cluster configuration is declared and Operators make it happen ○ Application deployments scheduler makes it happen ● GitOps in traditional environments requires automation/scripting, declarative environment minimizes or eliminates this need ● Declarations are yaml files which are easily Kustomize Argo CD - What is It? Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. ● Easily deploy applications in a declarative way ● Synchronizes cluster state with git repos