How to Configure JetBrains AI Kubernetes Permissions
You set up jetbrains ai kubernetes permissions by creating narrow RBAC roles for your user account. The editor assistant uses your local cluster context to read resources and run commands. Most teams start by sharing a personal admin context with the coding assistant. This broad setup lets the model read secrets, edit workloads, or delete live pods across namespaces. Scoping these rules down prevents an automated prompt from making bad changes in production. How jetbrains ai kubernetes permiss
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 jetbrains ai kubernetes permissions by creating narrow RBAC roles for your user account. The editor assistant uses your local cluster context to read resources and run commands. Most teams start by sharing a personal admin context with the coding assistant. This broad setup lets the model read secrets, edit workloads, or delete live pods across namespaces. Scoping these rules down prevents an automated prompt from making bad changes in production.
How jetbrains ai kubernetes permissions work in native RBAC
The assistant runs inside your local editor and inherits your local cluster credentials. It does not have its own cluster identity unless you build one for it. When you ask the tool to check a failing pod, it sends requests to the API server. Kubernetes RBAC checks these requests against the rules bound to your active user or service account.
In Kubernetes, a Role sets permissions inside one single namespace. A ClusterRole sets rules across the entire cluster and covers cluster-scoped objects like nodes. You link these rules to an identity with a RoleBinding or a ClusterRoleBinding. A RoleBinding grants rights inside one namespace, even if it points to a ClusterRole. A ClusterRoleBinding grants rights across every namespace in the cluster at once.
Keep in mind that native RBAC rules are only additive. There are no deny rules in standard Kubernetes RBAC. You must start with zero rights and add only the exact verbs the assistant needs. For safe code help, bind a read-only Role to a dedicated service account in a test namespace. Give that role basic verbs like get, list, and watch on pods and deployments.
Handling subresources like pod logs and command execution
Developers often ask their editor assistant to read app logs or run a quick check inside a container. In Kubernetes RBAC, these actions use subresources on the pod object. RBAC names resources using the exact path that appears in the API URL. You write a subresource rule by adding a slash between the parent resource and the subresource.
For example, reading pod logs requires permission on the pods log subresource. Running a command inside a container requires permission on the pods exec subresource. If you grant pods exec rights to an assistant, it can run arbitrary shell commands inside that container. You should leave exec rights out of the role you use for daily AI coding tasks.
AI Agent Permissions + Kubernetes RBAC: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native RBAC solves and what it leaves open
Native RBAC is great at controlling which API endpoints an account can reach. A tight Role stops the assistant from deleting deployments or reading cluster secrets. It keeps the model inside a single namespace and blocks write calls at the API server.
Still, static RBAC only checks who logs in and which API verb they call. It cannot inspect what individual commands or queries do while they run in flight. If an engineer needs pod log or exec rights to debug an issue, the assistant gets them too. Once the API server allows a log read, raw text flows straight back to the editor.
Pod logs often hold sensitive customer data like emails, phone numbers, card numbers, or national IDs. Native RBAC cannot rewrite matched fields in results before the text reaches the model prompt. In the same way, once RBAC allows an exec session, it cannot pause a dangerous shell command. Teams need a way to inspect commands and mask sensitive fields in real time.
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
Does the JetBrains assistant use its own Kubernetes account?
No, the assistant uses the local cluster context and credentials configured on the developer machine. To isolate its actions, you must create a separate service account and switch your context.
Can I add a deny rule to block secret access in Kubernetes RBAC?
No, Kubernetes RBAC permissions are purely additive and do not support deny rules. To block secret reads, you must create a new role that leaves out the secrets resource.
How do I let the assistant read pod logs without allowing container shell access?
Grant the get and list verbs on the pods log subresource inside your namespace Role. Do not include the pods exec subresource in that Role, which blocks remote shell commands.
Related guides
In this post