Openshift Developer License

Published
Length
3 min read

Luis Felipe Dias

All posts

You get an openshift developer license by joining the vendor developer program at no cost. This subscription lets you run local test clusters or use shared sandbox clusters for coding. Teams often start with this free tier to build and test apps on their laptops. Still, local clusters give users full admin power by default. When teams move those same role habits to shared clusters, permissions get too broad. A single mistake can then break workloads across the whole team. How an openshift dev

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 developer license by joining the vendor developer program at no cost. This subscription lets you run local test clusters or use shared sandbox clusters for coding.

Teams often start with this free tier to build and test apps on their laptops. Still, local clusters give users full admin power by default. When teams move those same role habits to shared clusters, permissions get too broad. A single mistake can then break workloads across the whole team.

How an openshift developer license works with cluster roles

Once you sign up for the program, you download the local cluster tool or log in to a shared sandbox. Under the hood, the platform uses standard Kubernetes role-based access control to manage permissions. Every rule in this system is additive, which means there are no deny rules.

A Role sets permissions inside one single namespace. A ClusterRole sets permissions across the entire cluster, including nodes and all namespaces. To give a user these permissions, you create a binding.

A RoleBinding grants access inside one namespace. It can point to a Role in that namespace or to a global ClusterRole. A ClusterRoleBinding grants permissions across the whole cluster at once.

On a local developer cluster, engineers often bind their accounts to broad cluster roles. This makes local testing fast and easy. On a shared sandbox, the platform locks your account into a specific namespace RoleBinding instead.

What native roles solve and what they leave open

Native roles and bindings do a good job of deciding who can talk to the cluster API. They let you split teams into separate namespaces. They also control who can view pod logs or open a shell inside a container.

In Kubernetes, actions like reading logs or running commands in a pod use subresources. You grant access to the pod log subresource or the pod exec subresource in a Role. Still, native roles stop checking once the connection starts.

OpenShift RBAC + Developer Portal Security: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

If a developer has permission to run commands in a pod, the cluster allows the whole session. The native role system does not check which shell commands the developer runs inside that pod. It also cannot mask sensitive fields like emails, phone numbers, card numbers, or national IDs in output.

Because permissions are additive, you cannot add a quick deny rule to block one risky command. You have to build a custom Role from scratch and remove broad bindings. Even then, a user with shell access can still run destructive scripts inside the container.

Moving from developer sandboxes to team clusters

An individual developer license is only meant for single-user testing and learning. You cannot use it to run production workloads or host shared team services. When your app is ready for real traffic, you must move to a supported team cluster.

That move is where permission habits matter most. If developers expect full cluster admin rights, they will ask for broad bindings in production. Instead, platform teams should limit namespace roles and watch what commands run inside pods.

Good access control checks every request in flight, not just the login step. It adds approvals for sensitive pod sessions and rewrites matched private fields in results.

Add request guardrails and response masking beside Kubernetes

Cluster roles and service accounts govern who reaches the Kubernetes API. Still, a broad role or agent can delete workloads or print sensitive values from ConfigMaps and logs. In practice, hoop.dev sits inline beside the API server as a sidecar for your Kubernetes API. For every production API call an agent or human sends, hoop.dev decides whether to pass, mask, block, or escalate it for review alongside RBAC.

With hoop.dev Kubernetes controls, guardrails allow listing Secret names while refusing reads of Secret data before execution, and data masking redacts matched keys in returned JSON responses and log streams in memory. Furthermore, hoop.dev holds SOC 2 Type II and is MIT licensed on GitHub.

Frequently asked questions

Can I use an openshift developer license for production apps?

No, the developer subscription is only for individual learning, coding, and testing. You must buy a standard commercial subscription before you run production workloads.

How do I restrict pod shell access on a shared cluster?

Remove the pod exec subresource from the user Role or ClusterRole. Because rules are only additive, you must edit the existing role rather than writing a deny rule.

What is the difference between a RoleBinding and a ClusterRoleBinding?

A RoleBinding grants permissions inside one specific namespace only. A ClusterRoleBinding grants permissions across all namespaces and cluster-wide resources like nodes.

The query runs. The emails stay hidden.