Envoy Gateway AKS
You set up envoy gateway aks by deploying its controller and custom resources to your cluster. Then you bind Kubernetes roles to control who can edit routing rules or inspect pods. Teams often start by giving developers broad cluster roles to speed up network debugging. When roles are too broad, engineers can alter production routes or run commands inside sensitive containers. How envoy gateway aks works with Kubernetes roles Running envoy gateway aks relies on standard Kubernetes role-based
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 envoy gateway aks by deploying its controller and custom resources to your cluster. Then you bind Kubernetes roles to control who can edit routing rules or inspect pods. Teams often start by giving developers broad cluster roles to speed up network debugging. When roles are too broad, engineers can alter production routes or run commands inside sensitive containers.
How envoy gateway aks works with Kubernetes roles
Running envoy gateway aks relies on standard Kubernetes role-based access control to manage team permissions. The API server checks rules in the rbac.authorization.k8s.io API group before allowing any change. In Kubernetes, permissions are purely additive, meaning there are no deny rules at all. You define a Role to grant permissions inside one specific namespace for your routing resources. If an engineer needs cluster-wide permissions, you define a ClusterRole instead.
A ClusterRole can cover cluster-scoped resources like nodes or namespaced resources across all namespaces. You then connect users to these rules with a RoleBinding or a ClusterRoleBinding. A RoleBinding grants permissions inside one namespace, even when it references a shared ClusterRole. A ClusterRoleBinding grants permissions across the entire cluster at once.
During setup and daily work, engineers also need to check pod logs or run commands. Kubernetes treats pod logs and command execution as subresources written with a slash in the API URL. Admins must grant separate permissions for the pod log subresource and the pod exec subresource. You can restrict subresource rules to specific pod names using the resource names field.
What native cluster roles solve and what they miss
Native Kubernetes roles do a good job of controlling who can create or update routing objects. You can lock down the namespace where the controller runs so only platform admins change core settings. App teams get a smaller RoleBinding in their own namespace to manage local routes. This separation prevents one team from breaking another team's ingress rules through the API server.
Still, Kubernetes role checks stop at the moment the API server approves the initial request. Once an engineer gets permission for the pod exec subresource, they open an interactive shell. Native roles cannot see or filter the individual shell commands that run inside that container. If a pod holds database keys or user traffic, anyone with exec rights can read them.
API Gateway (Kong, Envoy) + AKS Managed Identity: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
The same gap appears when engineers query backend services or inspect live data during an outage. Standard role bindings decide who logs in, not what commands or queries do in flight. Teams also face friction when sharing static cluster credentials or managing long-lived role bindings by hand. Even when logs capture API calls, they miss the raw output returned inside an interactive session. Sensitive fields like emails, phone numbers, card numbers, and national IDs return in plain text. To protect production clusters, teams need controls that work at the command and query level.
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
How do you limit team permissions for envoy gateway aks resources?
Create a Role in the team's namespace that only allows reading or updating their specific route objects. Bind that Role to the team group with a RoleBinding instead of using a ClusterRoleBinding.
Can Kubernetes RBAC block specific shell commands inside a pod?
No, Kubernetes RBAC only checks if a user can call the pod exec subresource on the API server. Once the session starts, native RBAC does not inspect or block individual shell commands.
Why should you separate pod log permissions from pod exec permissions?
Kubernetes treats logs and exec as separate subresources under the pod API path. Granting only the log subresource lets engineers read output without giving them an interactive shell.
Short role checks help teams work fast. Simple rules make each review clear. Good logs keep every team safe. Scoped keys stop bad changes early.
Teams test new role rules in staging first. Clear owner lists speed up each audit. Small role scopes cut down on risk. Regular log checks catch drift right away.
Related guides
In this post