Chapter 7. Cluster Management
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 you are just starting off in your GitOps journey or if you are a seasoned DevOps practitioner, this default setting helps administrators 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. The “hub” is the instance of Argo CD itself and is colloquially known as the “Argo CD Control Plane” in larger installations.
In this chapter, we will explore how clusters are managed in Argo CD, including how and where they are defined in the control plane, the ways in which they can be managed, and how we can set up different role-based access control (RBAC) policies to control their access in a multi-tenant situation.
Cluster Architecture
The cluster architecture of Argo CD is fairly straightforward; upon initial deployment, Argo CD has access to the local Kubernetes cluster (i.e., the Kubernetes cluster Argo CD was installed within). This access, as discussed ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access