Argo CD: Up and Running

Chapter 6. Cluster Management

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 7th chapter of the final book

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

Argo CD can deploy applications to the Kubernetes cluster that Argo CD is installed to without further configuration from administrators. This, out of the box, default setting makes it easy for administrators to get up and running and reap the benefits of Argo CD immediately. Whether just starting off in your GitOps journey, or if you are a seasoned DevOps practitioner; this default setting helps administrators to implement their solutions.

The simplicity of the Argo CD deployment can accelerate adoption beyond just a single team, to the point where management of additional clusters is needed and desired. Although you can deploy Argo CD instances to these additional clusters, Argo CD has the ability to add, manage, and deploy resources to additional clusters using a “hub and spoke” design. This hub and spoke design is colloquially known as “Argo CD Control Plane” in larger installations.

In this chapter, we will explore how clusters are managed in Argo CD including ...