kurtosis-tech Gateway
The Kurtosis gateway creates local port forwards to the engine and services running in a Kubernetes cluster.
When you need it
The gateway is required when running Kurtosis on Kubernetes. Without it, the local CLI cannot reach the engine pod in the cluster.
Not needed when using Docker backend.
Start the gateway
# Run in the background
kurtosis gateway &
# Or in a separate terminal
kurtosis gateway
Verify it's working
kurtosis engine status
If this returns engine info, the gateway is working. If it says "No Kurtosis engine is running" but you know the engine pod is up, the gateway isn't running.
Stop the gateway
pkill -f "kurtosis gateway"
How it works
The gateway:
- Finds the engine pod in the
kurtosis-engine-*namespace - Creates a local port forward to the engine's gRPC port
- When services are accessed, creates additional port forwards to service pods
- Port mappings shown in
kurtosis enclave inspectpoint to localhost via the gateway
Common issues
| Symptom | Fix |
|---|---|
No engine running but engine pod is up |
Start the gateway: kurtosis gateway & |
| Gateway crashes or disconnects | Restart: pkill -f "kurtosis gateway"; kurtosis gateway & |
| Port conflicts | Kill old gateway first: pkill -f "kurtosis gateway" |
| Services unreachable after gateway restart | Re-inspect enclave for new port mappings |