Kubernetes Exec

Kubernetes Exec gives a user an interactive shell inside a running Kubernetes container - the equivalent of kubectl exec - but brokered through the Bridge. The user picks a checkout, and a terminal opens inside the pod’s container right in the web interface. The session is recorded and every command is logged, so you get a full audit trail of what was run inside the cluster.

Kubernetes Exec is browser-only. There is no native listener and no port to configure - the shell always runs inside the Bridge web interface.

Granting access. Settings here enable Kubernetes exec for the deployment. To grant a person a shell into a pod, create a checkout - see the Kubernetes checkout options and a worked example.

Browser mode

Turn on browser mode to make Kubernetes Exec checkouts available.

bridge.yaml

k8s_exec:
  browser:
    enabled: true

When enabled, a user with a Kubernetes Exec checkout opens an in-browser terminal into the target pod’s container. The Bridge handles the connection to the cluster on their behalf; the user never needs cluster credentials or kubectl installed.

Shared options

bridge.yaml

k8s_exec:
  idle_timeout: 30m

Example

bridge.yaml

k8s_exec:
  idle_timeout: 30m
  browser:
    enabled: true

Option reference

Option	Type	Default	Description
`k8s_exec.idle_timeout`	duration	`30m`	Close a session after this much inactivity.
`k8s_exec.browser.enabled`	bool	`false`	Turn on the in-browser Kubernetes shell.

Last updated on July 6, 2026

HTTP/HTTPS Proxy Network Devices