Container Networking Best Practice


I just installed Minikube on a headless VM and have been running through some hello world type exercises. Very new to containers & container management.

I hit an issue I’m sure is quite common, and I was curious how most individuals and enterprises handle it.

So on this headless system, I ran minikube start | minikube hello-minikube. It is up successfully on

#: minikube service hello-minikube --url

How can I view this page from an outside network? I could try forwarding to my normal 192.168.0.—, or what about bridging my 192.168.0.— and 192.168.39.—

Before I try hacking it together, what is the SOP for this instance? Do enterprises have the pods deploy on reserved sections of their primary domain ex. or do they just have everything bridged together at the switch level, exposing requested ports?

Cluster information:

Kubernetes version: 1.20
Cloud being used: VM
Installation method: ?
Host OS: Ubuntu 18.04
CNI and version: ?
CRI and version: ?

What you’re looking for is something that can provide the loadbalancer service type. If you’re in a cloud, its often automatically provisioned for you. If you’re bare-metal or on prem, there are less options - but you can use something like metallb to serve that purpose.

This deck is a little old (content is still applicable), but should cover how all this works for you: