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

Declarative users

The Open Web Application Security Project (OWASP) – https://owasp.org – is a nonprofit foundation that does a lot of work with regard to web application security. Their most well-known project is the OWASP Top Ten (https://owasp.org/www-project-top-ten/), which is a list of the most important risks to consider when it comes to the security of our web applications. They update this list every few years. Currently, in their latest version, which is from 2021, so brand new, we have in first place Broken Access Control (it was in the fifth position on the previous 2017 list). Since the primary goal of the Top Ten is to bring awareness in the community about the major web security risks, we can understand with Broken Access Control being at the top that it is critical to do a proper setup for our users and the kind of access everyone gets in order to not violate the principle of least privilege. It would be common for our development teams to get write access...