From the course: Kubernetes Essential Training: Application Development

Unlock the full course today

Join today to access over 22,700 courses taught by industry experts or purchase this course individually.

Role-based access control in Kubernetes

Role-based access control in Kubernetes - Kubernetes Tutorial

From the course: Kubernetes Essential Training: Application Development

Start my 1-month free trial

Role-based access control in Kubernetes

“

- [Instructor] As well as the Worker Nodes, which are the VMs that our pods have been running on. Kubernetes has its Control Plane. This is the collection of software that orchestrates everything. And that's what we've been interacting with through various clients Kubectl, the Web Dashboard and infer.app. Workloads can also be Kubernetes aware, that is, they can know that they're running in a Kubernetes Cluster and they can talk to the Control Plane of that Cluster, the one that's looking after them. Sometimes, it does make sense for what I'll call an end user service. One of your pods in your application stack to talk to the Kubernetes Control Plane. Certainly a lot of what I'll call System Services need to do that. These are deployments that aren't part of Kubernetes, but they do similar system styles stuff affecting Kubernetes, augmenting it. The Ingress Controller is a good example of this. It's not part of…

Contents