Join us

Restricting cluster-admin Permissions

The article discusses the use of RBAC (Role-Based Access Control) in multi-user/multi-tenant Kubernetes clusters and its limitations in terms of subtracting permissions.

The author describes how they leveraged an admission controller using Kyverno to block a specific delete-all action that was causing issues in their CLI. They created a cluster policy that blocked cluster-admin and others from performing the specific action. The article highlights other potential use cases for this approach, such as preventing accidental deletion of critical resources, blocking fetching details of secrets in a specific namespace, and limiting deletes/updates/patches to specific users.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

Unsubscribe anytime. By subscribing, you share your email with @faun and accept our Terms & Privacy.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.

Join other developers and claim your FAUN.dev() account now!

Avatar

The FAUN

FAUN.dev()

@faun
The FAUN watches over the forest of developers. It roams between Kubernetes clusters, code caves, AI trails, and cloud canopies, gathering the signals that matter and clearing out the noise.
Developer Influence
3k

Influence

302k

Total Hits

3711

Posts