Flisk vs kind and minikube
kind and minikube run real Kubernetes on your laptop. Flisk does not.
| Task | Flisk Local dev stack | kind Kubernetes in Docker | minikube Local Kubernetes |
|---|---|---|---|
| Start a local environment | kind create cluster |
minikube start |
|
| Stop, keep state | flisk down |
No equivalent
|
minikube stop |
| Delete it | flisk down --prune-networksAlso removes this project's unused networks |
kind delete cluster |
minikube delete |
| Use a local image | No equivalent
|
kind load docker-image my-app:latest |
minikube image load my-app:latest |
| Open a service URL | flisk networks |
No equivalent
Use an ingress or LoadBalancer; see the kind guides. |
minikube service api |
| Read logs | flisk logs |
Different job, closest command.
kind export logsExports cluster logs to a directory, not a live tail. |
Different job, closest command.
minikube logsCluster logs for debugging minikube, not your code. |
| Check status | flisk status |
minikube status |
|
| List clusters | kind get clusters |
minikube profile list |
|
| Connect kubectl | No equivalent
|
kind export kubeconfig |
Different job, closest command.
minikube update-contextRepairs a stale kubeconfig entry after an IP or port change. |
| Diagnose the machine | flisk doctor |
No equivalent
No check command; `kind export logs` collects debug data. |
No equivalent
No check command; closest is `minikube logs`. |
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.