Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I use Minikube with the VirtualBox driver, and it is the only way that I have been able to deal with my slightly unusual networking requirements and do local dev with Kubernetes.

VirtualBox lets you forward ports from within the VM to your localhost directly, bypassing iptables and any default routes.

Our network uses a "no-split-tunneling" VPN, so most of the Docker networking solutions are completely unusable for me.

Kubernetes fortunately provides easy ways to enumerate the services that you intended to expose (via ingress, or similar) so it's absolutely trivial to script forwarding every exposed service or ingress to the localhost IP. I still am editing /etc/hosts file if I ever need to use a host-based route, and I have some interesting issues with SSL certificates that sometimes did not have the server name that I expected on them, but for the most part this works great for me.

I am a Mac user and showed my coworker who is a Windows user, we tried to do the same thing on his machine and it was even easier because there is no notion of privileged ports below 1024. So, it works the same way but with one less workaround.




> only way that I have been able to deal with my slightly unusual networking requirements

TBH they are not at all unusual. They are best-practices networking requirements.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: