The Wizard of Oz: The "Great and Powerful Oz", or also known as the "man behind the curtain."
"Oz RBAC Controller" is a Kubernetes operator that provides short-term elevated RBAC privileges to end-users through the native Kubernetes RBAC system. It aims to be the "man behind the curtain" - carefully creating Roles, RoleBindings and Pods on-demand that enable developers to quickly get their jobs done, and administrators to ensure that the principal of least privilege is honored.
Oz primarily works with two resource constructs - Access Requests and Access Templates.
Access Templates are defined by the cluster operators or application owners to create a "template" for how a particular type of short-term access can be granted. For example, the ExecAccessTemplate defines a particular target (DaemonSet for example) that a user can request access to, the Groups that are allowed to have that access, and rules around the maximum duration that the request can remain active.
Access Requests are created by end-users when they need access to a resource. RBAC privileges must be granted to users to even create the resource - but once that is done, actual access to the final target pod is controlled natively through the Kubernetes RBAC system, ensuring that we are not bypassing any standard internal RBAC controls.
Figured it was time to share this ... we've been using this controller for about a year now to dynamically provision ephemeral Pods and RBAC permissions for our engineers on-demand, without giving them broader access all the time.
The Wizard of Oz: The "Great and Powerful Oz", or also known as the "man behind the curtain."
"Oz RBAC Controller" is a Kubernetes operator that provides short-term elevated RBAC privileges to end-users through the native Kubernetes RBAC system. It aims to be the "man behind the curtain" - carefully creating Roles, RoleBindings and Pods on-demand that enable developers to quickly get their jobs done, and administrators to ensure that the principal of least privilege is honored.
Oz primarily works with two resource constructs - Access Requests and Access Templates.
Access Templates are defined by the cluster operators or application owners to create a "template" for how a particular type of short-term access can be granted. For example, the ExecAccessTemplate defines a particular target (DaemonSet for example) that a user can request access to, the Groups that are allowed to have that access, and rules around the maximum duration that the request can remain active.
Access Requests are created by end-users when they need access to a resource. RBAC privileges must be granted to users to even create the resource - but once that is done, actual access to the final target pod is controlled natively through the Kubernetes RBAC system, ensuring that we are not bypassing any standard internal RBAC controls.