Connect Kubernetes to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Kubernetes through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Kubernetes to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve Kubernetes in Runlayer
Add Kubernetes from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Install the Runlayer CLI so GitHub Copilot CLI can reach Kubernetes, which runs on the user’s machine.
GitHub Copilot CLI setup guide - 3
Sign in to Kubernetes
Sign in the way Kubernetes requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Kubernetes from GitHub Copilot CLI
Kubernetes’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
Kubernetes tools in GitHub Copilot CLI
Kubernetes reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Kubernetes call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot CLI as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more