Not every user needs unrestricted ability to create, modify, and delete resources. As the number of cluster nodes, applications, and team members increases, you’ll want to limit the resources your team members and applications can access, as well as the actions they can take.
The Role-Based Access Control (RBAC) framework in Kubernetes allows you to do just that. For example, it can help to ensure that developers only deploy certain apps to a given namespace or that your infrastructure management teams have view-only access for monitoring tasks.
Unfortunately, managing RBAC in Kubernetes comes with a certain amount of complexity and manual effort. In the article linked below we’ll provide some strategies for managing RBAC at scale.