Container Networking Best Practice
by stampede from LinuxQuestions.org on (#5CECY)
Hi,
I just installed Minikube on a headless VM and have been running through some hello world type exercises.
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 https://minikube.sigs.k8s.io/docs/start/ hello-minikube. It is up successfully on
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. 192.168.0.100-200? or do they just have everything bridged together at the switch level, exposing requested ports.
I just installed Minikube on a headless VM and have been running through some hello world type exercises.
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 https://minikube.sigs.k8s.io/docs/start/ hello-minikube. It is up successfully on
#: minikube service hello-minikube --urlHow can I view this page from an outside network? I could try forwarding to my normal 192.168.0.xxx, or what about bridging my 192.168.0.xxx and 192.168.39.xxx.
http://192.168.39.55:30918
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. 192.168.0.100-200? or do they just have everything bridged together at the switch level, exposing requested ports.