Connect Kubernetes to OpenCode
Give OpenCode governed access to Kubernetes through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Kubernetes to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode 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 OpenCode to Runlayer
Install the Runlayer CLI so OpenCode can reach Kubernetes, which runs on the user’s machine. Auto Sync can then write Kubernetes into OpenCode on macOS, Windows, and Linux.
OpenCode 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 OpenCode
Kubernetes’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
Kubernetes tools in OpenCode
Kubernetes reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Kubernetes call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more