kubevpn.dev

What It Is

KubeVPN is a local cloud-native development environment tool for Kubernetes. Its core goal is to connect a local PC to the network of a remote Kubernetes cluster, allowing developers to access in-cluster resources directly via Pod IPs, Service IPs, or service names. It also allows services in the remote cluster to access local services, and can intercept inbound traffic from remote services to the local machine, making local debugging of microservices easier.

Core Features and Ecosystem

Based on the main documentation, KubeVPN focuses on network connectivity and a complete local development loop. kubevpn connect creates a traffic manager, ServiceAccount, Role, RoleBinding, Service, Webhook, and Deployment, while also configuring tunnels, routes, and DNS. It supports connecting to Kubernetes clusters, domain name resolution, multi-cluster connections, reverse proxying, Service Mesh, Docker runtime mode, Sync mode, and multiple protocols. Its installation ecosystem is fairly complete: the client supports macOS, Linux, and Windows, and can be installed via brew, krew, snap, scoop, installation scripts, or GitHub Release. The server side can be installed with Helm, or automatically installed by the client during connection.

Pricing and Self-Hosting

The main content does not mention any commercial plans or pricing, only a Donate page with support for WeChat rewards and Alipay. Self-hosting is relatively clear: you can install the kubevpn server in your own Kubernetes cluster via Helm. It also supports private image registries and imagePullSecrets, and when images cannot be pulled from docker.io, you can specify or transfer images using --image or --transfer-image.

Pros and Cons

The main advantage is its focused use case: it addresses common pain points in Kubernetes development, namely “accessing the cluster’s internal network from local” and “replaying cluster traffic to local.” The documentation provides complete examples from installation to pinging a Pod IP and curling a Service IP, and the command system is fairly rich. The drawbacks are that the main content does not specify the open-source license, maintainer organization, or enterprise support. Usage involves TUN devices, routing, Webhooks, and RBAC resource creation, so it requires certain local machine permissions and cluster permissions. In mainland China, pulling images from docker.io may be restricted, so a private registry relay may be needed.

Who It’s For and Access from China

KubeVPN is suitable for Kubernetes microservice developers, platform engineering teams, and backend teams that need to jointly debug against remote clusters. In terms of access from China, the website itself does not indicate that it is blocked, but dependencies such as GitHub Release, raw.githubusercontent.com, and docker.io may be unstable in mainland China, so it is rated as “partially restricted.” Alternatives include Telepresence, mirrord, Nocalhost, and kt-connect.