Book Image

Argo CD in Practice

By : Liviu Costea, Spiros Economakis
Book Image

Argo CD in Practice

By: Liviu Costea, Spiros Economakis

Overview of this book

GitOps follows the practices of infrastructure as code (IaC), allowing developers to use their day-to-day tools and practices such as source control and pull requests to manage apps. With this book, you’ll understand how to apply GitOps bootstrap clusters in a repeatable manner, build CD pipelines for cloud-native apps running on Kubernetes, and minimize the failure of deployments. You’ll start by installing Argo CD in a cluster, setting up user access using single sign-on, performing declarative configuration changes, and enabling observability and disaster recovery. Once you have a production-ready setup of Argo CD, you’ll explore how CD pipelines can be built using the pull method, how that increases security, and how the reconciliation process occurs when multi-cluster scenarios are involved. Next, you’ll go through the common troubleshooting scenarios, from installation to day-to-day operations, and learn how performance can be improved. Later, you’ll explore the tools that can be used to parse the YAML you write for deploying apps. You can then check if it is valid for new versions of Kubernetes, verify if it has any security or compliance misconfigurations, and that it follows the best practices for cloud-native apps running on Kubernetes. By the end of this book, you’ll be able to build a real-world CD pipeline using Argo CD.
Table of Contents (15 chapters)
1
Part 1: The Fundamentals of GitOps and Argo CD
4
Part 2: Argo CD as a Site Reliability Engineer
7
Part 3: Argo CD in Production

Operating Argo CD

We will start this chapter by installing Argo CD with Kustomize using high availability (HA) manifests and go through some configuration options that we will perform while following the GitOps approach. We will make changes in the ConfigMap of a live Argo CD installation to see how we can modify different settings of Argo CD in a GitOps manner.

Then, we will look at the different Argo CD components, see what changes were introduced by the HA manifests, and what else we can do to make our installation a highly available one. While a Kubernetes cluster has a multi-control plane and worker nodes, it can still fail. Due to this, we will learn how to prepare for disaster recovery and move our installation from one cluster to another, including all the state.

Finally, we will discover what metrics are being exposed and how we can make the setup notify end users or send a custom hook to a CI/CD system when an application synchronizes successfully or not.

In this...