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