How to Configure Windsurf Kubernetes Approval
You set up windsurf kubernetes approval by combining user terminal checks with narrow cluster roles. This pairs local prompt confirmation with strict rules on the remote API server. Many teams start by giving their coding agent full admin rights on the cluster. That broad setup creates serious risk when an automated tool runs a bad command. A single wrong command can delete pods or expose secret values across every namespace. How windsurf kubernetes approval works in your local setup Cognitio
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 windsurf kubernetes approval by combining user terminal checks with narrow cluster roles. This pairs local prompt confirmation with strict rules on the remote API server. Many teams start by giving their coding agent full admin rights on the cluster. That broad setup creates serious risk when an automated tool runs a bad command. A single wrong command can delete pods or expose secret values across every namespace.
How windsurf kubernetes approval works in your local setup
Cognition renamed Windsurf to Devin Desktop on June 2, 2026. The tool keeps the same editor and features under this new name. Its built-in Cascade agent can run terminal commands with user permission. It uses a dedicated shell that loads your local profile and variables. Because it loads your shell setup, the agent inherits your local cluster keys. When the agent wants to run a cluster command, it asks you first. It can also reach external tools through configured model context servers. These local prompts form the first step of your approval workflow. You review the command text in the editor before the shell runs it.
Setting up cluster roles for agent tasks
Local prompts alone do not stop a bad command once you click approve. You also need strict role rules on the Kubernetes API server. Kubernetes role rules are purely additive and have no deny rules. You start with zero rights and add only the actions the agent needs. A regular role sets rules inside one single namespace. A cluster role covers the whole cluster or resources like nodes. You link these rules to an identity with a role binding. A cluster role binding gives those rights across every namespace at once. For an AI agent, you should prefer a namespace role binding. You can allow read actions on pods and pod logs for basic checks. Kubernetes treats pod logs and pod exec as separate subresources in the API. You should leave out pod exec rights so the agent cannot open shells.
What native setup solves and what it misses
This two-part setup solves basic login and broad permission problems. The local editor prompt stops the agent from running commands in secret. The cluster role stops the user account from changing namespaces it should not touch. Still, a big operational gap still remains in daily work. Native cluster roles only check who logs in and which resource they touch. They cannot check what an individual command or request does in flight. If a developer has rights to delete a pod, the agent does too. A tired engineer might click approve on a bad command by mistake. Also, pod logs or config maps might hold live emails or card numbers. Native roles return the full text and cannot mask those fields in results. Finally, local prompt clicks leave no central audit log for your security team. You cannot require a second teammate to approve a risky cluster change.
Approval Chains & Escalation + Kubernetes RBAC: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
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 sits inline as an open-source proxy, a sidecar for your Kubernetes API, without replacing RBAC. On every production call from an engineer or AI agent, hoop.dev decides to pass, mask, block, or hold it for human approval.
First, hoop.dev guardrails refuse banned methods, paths, or headers before they run or hold risky deletes for review. 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
Did Windsurf change its product name?
Yes, Cognition renamed Windsurf to Devin Desktop on June 2, 2026. It keeps the same editor features and the Cascade agent for running commands.
How does the agent get my cluster credentials?
The agent runs commands in a dedicated terminal that loads your shell profile. It uses the same environment variables and cluster keys that your user account uses.
Can Kubernetes RBAC block specific terminal flags?
No, Kubernetes roles only check the API resource, subresource, and action verb. They cannot inspect command arguments or require a teammate to approve a single action.
Related guides
In this post