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

Troubleshooting Argo CD

In this chapter, we will see how to address some of the issues you are most likely to run into during your day-to-day work with Argo CD. We will go through the installation procedure and see what can happen if we try to have more than one installation in the same cluster. This is a valid scenario for organizations that have many clusters deployed in development (dev) and production (prod) and need to split the load to different Argo CD instances. Then, we will discover how to use a specific version of Helm, different than the one embedded in the Docker image. Sometimes, this is needed because a newer version of a templating engine can bring some breaking changes and you would need more time to prepare for the upgrade, but you still want to have the performance improvements of the new Argo CD version. Argo CD has become much more stable in recent years—it is a mature application used by many organizations in production, but there are still cases when a...