Openshift Virtualization License
You get an openshift virtualization license as part of your existing Red Hat cluster subscription. You turn on the operator in your cluster to run virtual machines next to containers. Teams often set up this feature by giving engineers broad cluster admin roles right away. When roles are too broad, anyone can run commands inside any workload across the cluster. How an openshift virtualization license works with cluster roles Once your subscription is active, the platform treats virtual machin
Your coding agents run with your access.
Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.
You get an openshift virtualization license as part of your existing Red Hat cluster subscription. You turn on the operator in your cluster to run virtual machines next to containers. Teams often set up this feature by giving engineers broad cluster admin roles right away. When roles are too broad, anyone can run commands inside any workload across the cluster.
How an openshift virtualization license works with cluster roles
Once your subscription is active, the platform treats virtual machines just like native cluster objects. Each virtual machine runs inside a pod on your worker nodes. Because of this design, standard Kubernetes role-based access control governs every user action. You do not need a separate permission engine to manage who starts or stops machines.
In Kubernetes, a Role sets rules within one single namespace. A ClusterRole sets rules across the whole cluster and covers cluster-scoped objects like nodes. Permissions in this system are only additive. There are no deny rules in native role definitions. You link a Role to a user in one namespace with a RoleBinding. You use a ClusterRoleBinding to grant permissions across every namespace in the cluster.
When engineers fix a virtual machine or pod, they often need log or shell permissions. Kubernetes represents these actions as subresources in the API path. A rule for reading pod logs uses a slash between the resource and subresource name. The same pattern applies when an engineer opens an interactive shell into a running pod. If a role grants that subresource, the user can run commands inside the workload.
What native roles solve and what they leave open
Native roles and bindings do a good job of sorting users into basic groups. You can limit one team to a single namespace with a simple RoleBinding. You can also give read-only log rules to support staff while keeping exec rules restricted. This setup checks who is allowed to talk to the API server before a session starts.
Still, native role bindings stop checking once the API server approves the request. An exec subresource rule is an all-or-nothing pass into that pod or virtual machine container. Kubernetes RBAC decides who logs in, not what individual commands do in flight. Once inside the shell, a user can read local files or query connected databases.
OpenShift RBAC: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Teams also struggle with shared credentials and long-lived kubeconfig files on engineer laptops. If you restrict roles too much, developers cannot fix broken apps during an outage. If you grant broad roles across namespaces, you lose control over live shell commands. Native cluster logs show that an exec session started, not the sensitive data returned inside it. For example, native roles cannot rewrite emails, phone numbers, card numbers, or national IDs in output.
How to scope permissions before turning on virtual machines
Start by mapping which teams actually need to create or change virtual machine objects. Give those teams a namespace-scoped Role instead of a cluster-wide binding. Keep subresource rules for shell sessions out of default developer roles. Separate the people who view pod logs from the people who run live shell commands. Review your bindings often because additive rules can pile up and grant unwanted cluster reach.
Check Kubernetes API requests and responses on the wire
Kubernetes RBAC decides who may call the API server. RBAC does not check response payloads or split listing Secret names from reading Secret values when a role grants get access. With hoop.dev, you run an open-source HTTP proxy, a sidecar for your Kubernetes API. The kubectl client changes only the server address it talks to while RBAC stays in place.
On each call, hoop.dev guardrails read the method, normalized path, and headers to refuse bad deletes or full Secret reads with a 403 error. On the way back, hoop.dev data masking walks JSON responses by key and masks matched values in Secrets, ConfigMaps, and pod logs. Every request and verdict is logged without storing bearer tokens. View the project on GitHub.
Frequently asked questions
Does an openshift virtualization license cost extra on top of a cluster subscription?
Red Hat includes the virtualization feature in standard cluster subscriptions at no extra fee. You should check your specific subscription terms with Red Hat to confirm node core counts.
Can I use Kubernetes deny rules to block shell access to virtual machine pods?
No, Kubernetes role permissions are only additive and do not support deny rules. To block shell sessions, you must remove the exec subresource from the user's active roles.
Should teams use a RoleBinding or a ClusterRoleBinding for virtual machine owners?
Use a RoleBinding for app teams so their permissions stay inside one single namespace. Save ClusterRoleBindings for platform admins who must manage nodes and workloads across all namespaces.
Related guides
In this post