The cluster failed at 2:14 a.m. No one had touched it for hours. Yet an innocent misstep in permissions weeks ago had left a hole big enough to bring the platform down.
Cloud Foundry on Kubernetes offers power and flexibility, but without strong RBAC guardrails, it’s a matter of time before a simple change turns into an outage. Running modern workloads across teams means roles and permissions shape the safety of everything above them. RBAC, applied with precision, makes the boundary between smooth operations and chaos.
In Kubernetes, Role-Based Access Control defines who can do what. In a Cloud Foundry deployment on Kubernetes, the stakes are higher—because here, Kubernetes RBAC guardrails protect both your control plane and the app workloads riding on top. Without tight controls, push access to a namespace could escalate into cluster-wide privileges. Without segmenting permissions around orgs and spaces, bad updates can spill across environments.
Guardrails start with clear isolation between system components. ClusterRoles should only be handed to trusted automation and platform operators. Developers need scoped Roles tied to the smallest namespaces necessary. Service accounts must never default to wildcards. Audit logs should be on by default and watched in real time. Every RoleBinding and ClusterRoleBinding needs regular review and pruning.