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

Addressing day-to-day issues

In this section, we will discuss a few issues you would encounter on what we will call Day 2. If we mark Day 0 as the moment when we prepare the GitOps and Argo CD adoption and start working on proofs of concept (POCs) and Day 1 when we actually start implementing and deploying our GitOps solution, then Day 2 would be when we are in production, and we need to take care of the whole live setup. We went through important topics such as high availability (HA), disaster recovery (DR), and observability in Chapter 3, Operating Argo CD, and now we will see some issues that don’t fall into any of these categories.

Restarting components

Back in 2018 when we started with Argo CD, we had cases when we deployed a new version of one of our microservices and the synchronization just got stuck. The user interface (UI) showed that the reconciliation loop was ongoing, but nothing was happening, there was no progress, and no error was displayed. That’...