←back to thread

KubeVPN: Revolutionizing Kubernetes Local Development

(github.com)
67 points naison | 3 comments | 20 Feb 25 05:09 UTC | HN request time: 0.001s | source
Show context
techn00 ◴[20 Feb 25 15:47 UTC] No.43116119[source]▶
My ideal k8s dev env (I wonder if any of the tools do this):

- local on my machine.

- ingress with https + subdomains integrated with mDNS (so I can access the services easily from my phone when developing mobile apps). mDNS also makes sure that other devs can set it up locally for themselves.

- easily swap what I'm working on, if I have 3 services A, B, C, while I'm working on A locally, I want B and C to run in the cluster and to be able to interact with them, same if I'm working on B, A and C should run in the cluster.

replies(2): >>43116486 #>>43119587 #
jcollins ◴[20 Feb 25 16:14 UTC] No.43116486[source]▶
Tailscale Operator for Kubernetes sounds like it'd fit your second bullet point. It's has a really good experience. I've only used for my person homelab but I've been more than impressed by it.
replies(1): >>43117027 #
1. techn00 ◴[20 Feb 25 16:50 UTC] No.43117027[source]▶
It could however I specified mDNS so other developers won't be required to use tailscale (or to run a dns server)
replies(1): >>43117248 #
2. jcollins ◴[20 Feb 25 17:06 UTC] No.43117248[source]▶
Fair. Making https work with mDNS seamlessly sounds like work (i.e. local CA would be needed I think). It would make things nice though.
replies(1): >>43121854 #
3. craftkiller ◴[20 Feb 25 23:25 UTC] No.43121854[source]▶
Instead of mDNS, they could update a DNS record for a subdomain (techno00.dev.thecompany.com, preferably under a different domain than your real one) to their local IP address and then do the DNS-01 challenge on LetsEncrypt to get a valid TLS cert for the subdomain. Then the only problem is some routers block DNS responses with RFC-1918 IP addresses, but everyone is using DoT/DoH by now, right? ... right?