#kubernetes #rbac #devops #fullstackdevelopment
So far we have accessed everything from our Kubernetes cluster without any restrictions. But in real time, we’ll have multiple nodes, namespaces, deployments, replica sets, pods, services, and many other Kubernetes resources. Also, we will have many users accessing these cluster resources. When we don’t have any restrictions, there may be chances of deleting these resources accidentally.
So, it’s wise to impose restrictions to create, modify, and delete resources based on some role. For example, we should ensure that developers can only deploy certain apps to a given namespace or that our infrastructure management teams have read-only access for monitoring tasks, and the admin can do everything. In this chapter, we’ll be learning how to restrict access to Kubernetes resources using the RBAC framework with complete hands-on.
Manifests: https://github.com/pelthepu/Kubernetes/tree/master/resources/rbac
Please give a Like and Subscribe to the channel - https://bit.ly/pavanelthepu
Timestamps:
0:00 - Intro
01:03 - Authentication vs Authorization
02:59 - Users and Groups
09:09 - Role and RoleBinding
13:31 - ClusterRole and ClusterRoleBinding
16:16 - Service Accounts
My other courses:
Docker Complete Course: https://youtu.be/1eVy_iWrc20
Thank you very much!