Flisk vs Telepresence and mirrord
These connect your laptop to a remote cluster. Flisk needs no cluster.
| Task | Flisk Local dev stack | Telepresence Bridge to a cluster | mirrord Run locally in the cluster |
|---|---|---|---|
| Connect to the cluster network | telepresence connect |
Different job, closest command.
mirrord exec microsocksNeeds microsocks. Runs a SOCKS proxy in the cluster's network. |
|
| Take over a service's traffic | No equivalent
|
telepresence intercept api --port 8080:http |
mirrord exec --steal --target pod/api python main.pyOr set incoming to steal in the config file. |
| Copy traffic, keep the service | No equivalent
|
telepresence wiretap api --port 8080:http |
mirrord exec --target pod/api python main.pyMirroring is the default mode. |
| Run a local process in the cluster's context | telepresence ingest api -- python main.pyBrings env vars and mounts; no traffic is routed. |
mirrord exec --target deployment/api python main.py |
|
| List services | |||
| Check status | flisk status |
telepresence status |
Different job, closest command.
mirrord operator statusReports cluster and Operator status; the Operator is a Teams feature. |
| Disconnect | flisk down |
telepresence quit |
|
| Verify the config | flisk config verify |
Different job, closest command.
telepresence config viewShows the current config; it does not validate it. |
No equivalent
A hidden verify-config exists; the docs do not list it. |
| Diagnose | flisk doctor |
Different job, closest command.
telepresence gather-logsCollects logs into a zip file; it runs no checks. |
Different job, closest command.
mirrord diagnose latencyOnly measures latency to the target. |
No task matches. Try a shorter search.
- Same job
- Different job: closest command, not a swap
- Blank: no equivalent
- Hover a cell for ↗︎ source and i note. Click a command to copy it.