Vvs EKS

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a vvs eks workflow by binding identity roles to Kubernetes RBAC rules. This lets your team run cluster commands with scoped permissions in one namespace or across all nodes. Most teams start by mapping group roles to broad cluster roles for speed. When roles are too broad, one engineer can change workloads or read logs across every namespace. How a vvs eks role setup works in Kubernetes Kubernetes uses role-based access control to check what a user or service can do. You turn 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 set up a vvs eks workflow by binding identity roles to Kubernetes RBAC rules. This lets your team run cluster commands with scoped permissions in one namespace or across all nodes. Most teams start by mapping group roles to broad cluster roles for speed. When roles are too broad, one engineer can change workloads or read logs across every namespace.

How a vvs eks role setup works in Kubernetes

Kubernetes uses role-based access control to check what a user or service can do. You turn this mode on at the API server level. Every rule in this system is additive, which means there are no deny rules. You start with zero permissions and add rules for each needed action.

A Role sets permissions inside one single namespace. A ClusterRole is not tied to a single namespace. It can cover cluster-wide items like nodes, or resources across every namespace. To give these rules to a user, you create a binding.

A RoleBinding grants permissions inside one namespace. It can point to a Role in that same namespace or to a shared ClusterRole. If a team needs permissions in every namespace at once, you use a ClusterRoleBinding. This structure lets you reuse one ClusterRole across many teams while keeping each team in its own namespace.

Controlling pod logs and shell commands

Kubernetes splits some API actions into subresources. When you read pod logs or run a command in a container, you use a subresource. In RBAC rules, you write the main resource name, a slash, and the subresource name. For example, reading pod logs uses the pods and log path.

Teams often want to let developers read logs without letting them open a shell. You can do this by granting read access to the log subresource while leaving out the exec subresource. If you include the exec subresource, the user can run interactive commands inside that container. You can also limit rules by resource name, though create rules only apply name limits to top-level resources.

EKS Access Management: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What native cluster roles solve and what they leave open

Native roles and bindings do a great job of deciding who can reach the cluster API. They keep teams in their own namespaces and stop unauthorized users from listing pods or nodes. You can separate read-only viewers from operators who deploy new apps.

Still, a native role check stops at the API call boundary. Once a user has permission to run exec on a pod, Kubernetes does not check the commands inside that shell. The API server knows a session started, but it does not filter what runs inside the container. It also does not mask sensitive values like emails, phone numbers, card numbers, or national IDs in output. Teams that need command-level checks or data masking in results must add controls above the base cluster role.

Govern kubectl and API calls in flight

Identity providers and Kubernetes RBAC decide who logs into a cluster. They cannot redact keys inside returned JSON objects or hold a risky delete call for review. By design, hoop.dev runs as an open-source proxy, a sidecar for your Kubernetes API, checking requests and responses without replacing RBAC.

First, hoop.dev guardrails refuse banned methods, paths, or headers before they run. Next, hoop.dev data masking rewrites sensitive keys in returned Secret, ConfigMap, and log responses in memory, and writes each decision to the audit trail. Explore the repo on GitHub.

Frequently asked questions

Can I write a deny rule in Kubernetes RBAC for a vvs eks setup?

No, Kubernetes RBAC rules are only additive. You cannot write a rule that denies a specific action out of a broader role. Instead, grant a smaller base role and add only the exact permissions each team needs.

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 namespaces at once. You can pair a RoleBinding with a ClusterRole to reuse standard rules inside a single namespace.

How do I let developers read pod logs without giving them shell access?

Create a Role that grants permissions on the pod log subresource only. Do not include the pod exec subresource in that role. Bind that role to your developer group in their target namespace.

The query runs. The emails stay hidden.