←back to thread

KubeVPN: Revolutionizing Kubernetes Local Development

(github.com)
67 points naison | 1 comments | 20 Feb 25 05:09 UTC | HN request time: 0s | source
Show context
remram ◴[20 Feb 25 16:28 UTC] No.43116704[source]▶
I don't really understand the point of this. I have a production cluster and I develop locally. My dev environment is not connected to the production cluster. That seems super dangerous.

My dev environment has the database with mock data, the backend, etc all running there. I would never connect to the production cluster. I don't need to VPN into another cluster to run locally.

Even if I have a dev cluster/namespace, then I will run the code I'm currently developing there. That's the point of a dev cluster. (Tilt for example can do both: a local cluster (minikube/k3d/...) or a remote test cluster)

I don't understand in what situation you have an app that needs to partially run in the cluster and needs to partially run on your machine.

replies(2): >>43116864 #>>43116868 #
kube-system ◴[20 Feb 25 16:40 UTC] No.43116864[source]▶
> the database

> the backend

Many k8s clusters are quite a bit more complicated than a single database and single backend. Some have dozens or hundreds of deployments. Even if you have the horsepower to run large deployments on your system, you will have problems wiring it all up to match production.

replies(2): >>43116932 #>>43117848 #
1. ◴[20 Feb 25 17:48 UTC] No.43117848[source]▶