1. Introduction to Kubernetes
RBAC

2. About Me Name: Jainish Shah Github: @jainishshah17

3. What is RBAC?
Role-based access control (RBAC) is an approach that is used for restricting access to users and applications on the system/network.
RBAC is used by Kubernetes for authorization, for example giving access to a user, adding/removing permissions and setting up rules, etc.
By default, RBAC is enabled in Kubernetes.

4. Why RBAC?
Each of users in kubernetes cluster needs to some amount of security from one another.
There could be cases, where a member of one team is interfering with the other members, work accidentally

5. Role
Role in Kubernetes Role-Based Access Control defines a notion of a verb like get or list and a set of nouns like pod volumes etc. So, a role defines what you can do to a set of resources. It contains a set of rules which define a set of permission.
A Role always sets permissions within a particular namespace; when you create a Role, you have to specify the namespace it belongs in.

6. RoleBinding
A role binding grants the permissions defined in a role to a user or set of users.
It holds a list of subjects (users, groups, or service accounts), and a reference to the role being granted.
A RoleBinding grants permissions within a specific namespace.

7. ClusterRole ClusterRole, is a non-namespaced resource.
The resources have different names (Role and ClusterRole) because a Kubernetes object always has to be either namespaced or not namespaced; it can’t be both.
ClusterRole is used to define a role cluster-wide.
You can use a ClusterRole to:
define permissions on namespaced resources and be granted within individual namespace(s)
define permissions on namespaced resources and be granted across all namespaces
define permissions on cluster-scoped resources

8. ClusterRoleBinding
ClusterRoleBinding is used to grant permission to a subject on a cluster-level in all the namespaces.
It can provide you with permissions for cluster resources and it can also provide you with permissions for resources within any namespace within a cluster.

9. Demo