Chapter 6. Authentication and Authorization
Included as part of the standard platform deployment, Argo CD contains a default management user providing unrestricted access to configure the platform using either the UI or via the API/CLI. By providing this functionality out of the box, it simplifies the getting started experience and enables end users to realize the capabilities provided by Argo CD and the concepts embraced by GitOps methodologies.
As adoption grows beyond a single individual managing and utilizing Argo CD, there becomes a need to support additional users aside from a single elevated management user along with integrating with a centralized user management system, such as LDAP or a compatible OIDC provider. While at the same time, when providing the capability to support additional users, there must also be a way to define and govern the level of access that each entity is entitled to.
In this chapter, we will explore how users are managed in Argo CD, including where and how they are defined, the ways that they can perform actions against the tool, and the capabilities to define role-based access control (RBAC) policies to govern their access.
Managing Users
While Argo CD supports the ability to define and leverage multiple users, upon initial deployment, there is only a single user available for use—“admin.” The admin user, as discussed previously, is provided both as a convenience for quickly getting up to speed with the capabilities provided by Argo CD and for ...
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