How to Configure JetBrains AI Kubernetes Credentials

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up jetbrains ai kubernetes credentials by linking your local cluster file to the editor. The editor reads your active context and uses those keys for cluster tasks. Many teams start by giving developers broad cluster admin roles to move fast. Broad roles let an assistant read sensitive data or change live workloads by mistake. A safer setup uses tight role rules that limit what the user can run. How jetbrains ai kubernetes credentials work in your editor Your editor does not hold a se

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 credentials by linking your local cluster file to the editor. The editor reads your active context and uses those keys for cluster tasks. Many teams start by giving developers broad cluster admin roles to move fast. Broad roles let an assistant read sensitive data or change live workloads by mistake. A safer setup uses tight role rules that limit what the user can run.

How jetbrains ai kubernetes credentials work in your editor

Your editor does not hold a separate set of cluster keys for the assistant. Instead, the editor uses the local config file on your machine. When the assistant suggests or runs a task, it uses your current user role. The cluster API server checks your token against Role and ClusterRole rules. In Kubernetes RBAC, rules are purely additive and include no deny rules. A Role sets rules inside one namespace for that specific project. A ClusterRole sets rules across the whole cluster and covers nodes or all namespaces. You attach these rules to a user with a RoleBinding or a ClusterRoleBinding. A RoleBinding grants permissions inside one namespace, even if it points to a ClusterRole. A ClusterRoleBinding grants permissions across the entire cluster at once. To keep the assistant safe, bind your local user to a small Role. Grant read rules on pods and logs so the tool can check app health. Leave out write rules on secrets or live deployments unless you need them.

What native roles solve and where gaps remain

Native RBAC does a good job of deciding who can log in. It blocks users from touching namespaces or resource types they should not use. You can even write rules for subresources such as pod logs or pod exec. RBAC names these subresources with a slash in the rule definition. This lets you allow log reading without allowing shell commands inside a pod. Still, static role bindings leave a large operational gap during daily work. Once a role grants pod exec or secret read rules, every command goes through. Native RBAC cannot check what a specific command does while it runs. It also cannot mask sensitive text inside pod logs before the editor reads them. If a log line holds emails, phone numbers, card numbers, or national IDs, it stays visible. Also, developers must keep raw cluster tokens stored on their laptops. If a local token leaks, an attacker gets the full power of that role. Teams need a way to check individual commands in flight and remove local keys.

Check Kubernetes API requests and responses on the wire

Kubernetes RBAC decides who may call the API server. RBAC does not check response payloads or split listing Secret names from reading Secret values when a role grants get access. With hoop.dev, you run an open-source HTTP proxy, a sidecar for your Kubernetes API. The kubectl client changes only the server address it talks to while RBAC stays in place.

Ephemeral Credentials + Kubernetes RBAC: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

On each call, hoop.dev guardrails read the method, normalized path, and headers to refuse bad deletes or full Secret reads with a 403 error. On the way back, hoop.dev data masking walks JSON responses by key and masks matched values in Secrets, ConfigMaps, and pod logs. Every request and verdict is logged without storing bearer tokens. View the project on GitHub.

Frequently asked questions

Where does the editor find my cluster keys?

The editor reads your standard local kubeconfig file on your workstation. It uses the active context and token that you set up for your command line tool.

Can I block specific actions with a Kubernetes deny rule?

No, Kubernetes RBAC rules are purely additive and do not support deny rules. You must start with zero permissions and only add the exact rules a user needs.

How do I let the assistant read logs without running pod shells?

Grant read permissions on the pod log subresource in your namespace Role. Leave out permissions for the pod exec subresource so shell commands fail.

The query runs. The emails stay hidden.