Argo CD: Up and Running

Chapter 7. Multi-Tenancy

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 8th 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].

One of the things that make Argo CD so popular is the user experience that it provides. From the UI to the rich RBAC system; Argo CD continues to not only be the GitOps tool of choice, but also a great choice in providing a rich user experience as well. With that in mind, Argo CD also extends multi-tenancy beyond just basic RBAC. It also has the ability to granularly set access controls based on the actor performing the action (user, group, or automated service account), which resource is being accessed, and what action is being performed.

In Chapter 6 - Authentication and Authorization, you learned about RBAC and its various uses. In this chapter, we are going to extend that knowledge by introducing the Argo CD AppProject concept and how to manage RBAC configurations on a per-Project basis. We are going to start off by demonstrating different Argo CD Deployment models. Then, we are going to explore, in detail, what Argo CD AppProject’s are and how to effectively use ...