Role-based access control
In production systems, you need to allow different users different levels of access to certain resources; this is known as role-based access control (RBAC). This section will take you through how to configure RBAC in AKS, and how to assign different roles with different rights. The benefits of establishing RBAC are that it not only acts as a guardrail against the accidental deletion of critical resources but also that it is an important security feature that limits full access to the cluster to roles that really need it. On an RBAC-enabled cluster, users will be able to observe that they can modify only those resources to which they have access.
Up till now, using Cloud Shell, we have been acting as root, which allowed us to do anything and everything in the cluster. For production use cases, root access is dangerous and should be restricted as much as possible. It is a generally accepted best practice to use the principle of least privilege (PoLP) to log...
