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