The presentation discusses the basics of Kubernetes Role-Based Access Control (RBAC) and how it can be used to create a flexible system that allows teams to work together in deploying cloud-native apps.
- Kubernetes is an operating system that turns servers or cloud data centers into one big computer
- RBAC is the authorization part of the API that lets teams share and block off parts of the computer to run the system
- RBAC is composed of RBAC basics, identity details, common misunderstandings, RBAC's limitations, auditing, and useful patterns for real-world implementations
- RBAC's subjects are users and groups, and apps
- The presentation includes a performance art piece and live demos to illustrate the points discussed
The speaker started the presentation with a performance art piece that highlighted the challenges of working together with people on hard systems. He emphasized the importance of using the tools to have people and processes work together in solving bigger problems for society, humanity, and making money with capitalism. He compared Kubernetes to a big expensive but super-fast Formula One car of a promise machine that requires a whole community to run it around the track. The RBAC API is crucial in letting teams share and block off parts of the computer to run the system.
Every day, someone new wants to deploy their cloud-native app... then it ends up running on Kubernetes! Suddenly, all sorts of people have questions about the app and need to make changes. Developers, SREs, Product Folks, and Organization Leaders all have different needs and levels of experience with the myriad of Kubernetes resources needed for an app, so how should platform teams give folks the access they need? This session will show how the basics of Kubernetes Role-Based Access Control (RBAC) compose together to create a flexible system that lets teams work together. Come learn about: - RBAC Basics - The Details of Identity - Common Misunderstandings - RBAC's Limitations - Auditing - Useful Patterns for Real-world Implementations This session will also include some fun, relatable Live Demos! Expect to leave better equipped to support the transparent, collaborative, self-service ownership of a DevOps culture.