The first time I saw it happen, the screen filled with hundreds of roles I didn’t create.
What started as a routine look at permissions in K9S turned into a shock: a cascade of large-scale role creation flooding the cluster. The Role Explosion. It’s a moment many teams never forget—when Kubernetes RBAC spirals out of control without warning.
K9S is a powerful terminal UI for Kubernetes. It gives you speed, agility, and a clear view into your resources. But when a Large-Scale Role Explosion hits, K9S becomes the flashlight in a collapsing tunnel. In seconds, you see the problem: dozens or hundreds of new Roles or RoleBindings populating the namespace map, permissions ballooning beyond any safe boundary, and audit logs swelling with noise.
The root causes differ. Sometimes it’s bad automation logic pushing repetitive Role creation. Sometimes it’s cluster misconfigurations combining with rollout scripts. Other times, access controls are too loose and rogue processes operate outside guardrails. But the effect is always the same: RBAC turns unwieldy. Permissions multiply, risk grows, and restore points start to feel like lifeboats.