Articles

Add log analytics to your local Kubernetes dev environment with Elasticsearch, Kibana, and Filebeat — all running on vCluster inside Docker.

Metrics tell you something is wrong. Logs tell you why. In Part 2 of this observability series, we deploy a complete ELK-based log analytics stack on a local multi-node Kubernetes cluster powered by vCluster — no cloud account, no VMs, just Docker and a few commands.

Metrics, dashboards, alerting, and long-term storage, deployed on a multi-node Kubernetes cluster that runs entirely in Docker

Observability isn't optional, it's foundational. This guide walks through deploying Prometheus, Grafana, Thanos, and RustFS on a local multi-node Kubernetes cluster powered by vCluster. No cloud account required. No VMs. Just Docker and a few commands.

A web dashboard for all your local vind clusters with projects, team management, role-based access, and automation through access keys

The CLI is great for daily dev work. But when you need to see all your clusters at a glance, organize them into projects, manage team access, or hand off a demo environment, the vCluster Platform UI takes vind from a better KinD to a real cluster management platform. Day 7 of the 7 Days of vind series.

Pause clusters and resume where you left off, pull locally built images in 45ms, install Cilium, and map custom ports to your local cluster

With KinD, you delete your cluster at the end of the day and recreate it tomorrow. With vind, you pause it and resume exactly where you left off. Deployments, services, PVCs, all still there. Day 6 covers sleep/wake, registry proxy, custom CNI, and more.

Drop setup-kind from your GitHub Actions and get built-in registry proxy, automatic log export, and multi-cluster CI workflows with setup-vind

If you're using setup-kind in GitHub Actions, you're still loading images manually and missing automatic log exports. setup-vind is a drop-in replacement with built-in registry proxy, automatic artifact export, and multi-cluster support. Day 5 of the 7 Days of vind series.

Run your control plane locally in Docker, join a real cloud VM as a worker node over VPN, and schedule pods across both

Local Kubernetes tools stop at your laptop. vind doesn't. Join a GCP Compute Engine instance as a real worker node to your local cluster over an encrypted VPN tunnel. Test GPU workloads, mixed architectures, and hybrid setups. Day 4 of the 7 Days of vind series.

Create a multi-node local cluster in Docker and test pod distribution, node drains, affinity, and anti-affinity, just like production

Single-node clusters can't test scheduling. With vind, spin up a 4-node cluster in Docker, deploy across workers, drain nodes, and test affinity rules, real Kubernetes behavior on your laptop. Day 3 of the 7 Days of vind series.

Install vind, create a local Kubernetes cluster, and deploy nginx with a working LoadBalancer — in under 3 minutes

KinD needs MetalLB for LoadBalancer services. vind has it built in. In Day 2 of the 7 Days of vind series, we walk through creating a cluster, deploying nginx, and hitting a real LoadBalancer IP, all running in Docker on your laptop.

KinD works until it doesn't. vind picks up where it leaves off.

KinD works, until you need LoadBalancer services, multi-node setups, or the ability to pause and resume clusters. vind gives you a production-like local Kubernetes experience in Docker with features KinD simply doesn't have. Day 1 of the 7 Days of vind series.