Free Version of Openshift

Published
Length
3 min read

Luis Felipe Dias

All posts

You can get a free version of openshift through community builds or developer sandboxes. Teams use these setups to test apps and learn cluster rules without license fees. Most engineers start with default admin accounts to deploy workloads fast. Broad permissions create big risks when multiple people share the same cluster. One bad command can delete shared pods or expose secret keys. How roles work in a free version of openshift Every OpenShift cluster runs on a core Kubernetes engine. This

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 can get a free version of openshift through community builds or developer sandboxes. Teams use these setups to test apps and learn cluster rules without license fees. Most engineers start with default admin accounts to deploy workloads fast. Broad permissions create big risks when multiple people share the same cluster. One bad command can delete shared pods or expose secret keys.

How roles work in a free version of openshift

Every OpenShift cluster runs on a core Kubernetes engine. This engine uses role-based rules to control who can touch cluster objects. A Role sets permissions inside one single namespace. A ClusterRole sets permissions across the whole cluster. It covers cluster nodes, non-resource endpoints, and namespaced items everywhere.

In this system, permissions only add up. There are no deny rules in native role definitions. You start with zero rights and gain them through bindings. A RoleBinding gives a user or team rights inside one namespace. It can point to a local Role or a broad ClusterRole. A ClusterRoleBinding gives those rights across every namespace in the cluster.

The API server checks these rules on every request. Some actions target subresources like pod logs or pod command execution. Rules write these subresources with a slash between the resource and the action. Admins must grant rights to both the pod and the specific subresource.

What native cluster roles solve and what they miss

Native roles are great for sorting out who can view or launch apps. You can lock a developer into one test namespace with a simple RoleBinding. This stops them from changing nodes or reading secrets in other projects. It keeps a shared test cluster neat and prevents accidental deletions across teams.

Still, native role checks stop at the API door. Once a role lets an engineer run commands in a pod, the cluster steps back. The API server checks if the user can open the shell session. It does not inspect the bash commands typed inside that open session. It also does not filter the data that prints back to the screen.

DPoP (Demonstration of Proof-of-Possession) + OpenShift RBAC: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Subresource rules have another limit in the native API. Name restrictions on create actions only apply to top-level resources, not subresources. This makes it hard to lock shell sessions down to one named pod. Plus, any app database credentials stored inside the pod sit open to the user. If a test pod holds real emails, phone numbers, or card numbers, they print out raw.

Securing container sessions beyond cluster roles

Teams often outgrow basic sandbox clusters and move to shared staging setups. At that point, relying only on static role bindings leaves too much open. Engineers need a way to fix broken pods without holding permanent admin keys. Security teams need a clear log of every command run inside a container.

Splitting cluster entry from in-session control solves this problem. Keep native roles tight so users can only view basic pod status. Handle deep debugging and database checks through a dedicated control point. That way, you can check each command and mask sensitive fields like national IDs in flight.

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 restrict native role rules with a deny rule?

No, native Kubernetes role permissions are only additive. You cannot write a rule that subtracts rights from a user. You must build access from the ground up using smaller roles.

What is the difference between a RoleBinding and a ClusterRoleBinding?

A RoleBinding grants permissions inside one specific namespace only. A ClusterRoleBinding grants permissions across the entire cluster and all of its namespaces. Both can reference a ClusterRole, but they apply it at different scopes.

Do pod exec permissions log the commands typed inside a container?

Native RBAC only checks if a user is allowed to start the exec subresource call. It does not parse, block, or log the individual shell commands run inside that session. Teams need extra session controls to record shell input and output.

The query runs. The emails stay hidden.