Exposing ingress to a remote host

[suren-khatana]

Hi,
I am running a vagrant box using virtual box (running headless ubuntu 18.04) on windows 10 host machine.
Inside the virtual box, I have minikube set up using docker as the vm-driver
minikube start --memory=6144 --cpus=2 --disk-size=40g --vm-driver=docker --bootstrapper kubeadm --kubernetes-version=1.17.4
My application is exposed via an ingress to the ubuntu machine running inside virtual box and I am able to access the application via wget/cURL

On doing minikube IP it gave me the IP of the docker container in which minikube runs

Some additional configuration info -

Vagrant file -

I would like to access the application from my windows machine's browser , any idea how to achieve that ? vagrant port forwarding doesn't seem to help.

Thanks

[priyawadhwa]

Hey @surensinghkhatana I'm not familiar with vagrant but it looks like you have this in your config:

  config.vm.network "forwarded_port", guest: 80, host: 8080

You could try using minikube tunnel to forward your service to a local port in the ubuntu VM, and replace "guest: 80" with the port that provides. Then, the application should be forwarded to port 8080 on your Windows host.

Let me know if that would helps. More info on tunnel here

[suren-khatana]

Hi @priyawadhwa ,
Thanks for your comment.
I have removed vagrant from the picture now. Minikube is running inside a docker container in a Ubuntu VM running on virtual box.

Some configuration info from my env :

I don't have any LoadBalancer service in my k8s cluster. I tried using minikube tunnel but couldn't understand how to expose a port on Ubuntu VM which could then be mapped to a port on my Host (windows) machine enabling the access to https://fg.iam.example.com/am from my host browser ?

[sharifelgamal]

I think what you're looking for is ssh port forwarding

[ilya-zuyev]

@surensinghkhatana does ssh port forwarding work for you?

[suren-khatana]

@ilya-zuyev @sharifelgamal Thanks for your reply, unfortunately it doesn't work still.
Minikube ip as shown in the picture (from with in the VM) is not reachable from my host machine ..

[suren-khatana]

Result of ifconfig inside the VM

[medyagh]

the problem is, our current Docker driver only listens on 127.0.0.1, which is for security reasons.

we could offer a --listen-remote flag for users who need to listen on non local hosts.

have you tried running minikube driectly on your host ? with either vbox or docker driver?

[vrybas]

the problem is, our current Docker driver only listens on 127.0.0.1, which is for security reasons.
we could offer a --listen-remote flag for users who need to listen on non local hosts.

@medyagh having this flag would be nice. Is there a temporary solution to make minikube running with docker driver inside Virtualbox VM listen for all requests?

[vrybas]

@surensinghkhatana were you able to make minikube to listen to external requests?

[suren-khatana]

@vrybas I decided to move on with microk8s ..

[priyawadhwa]

Hey @surensinghkhatana sorry to hear that! Looks like there currently isn't a solution for this is in minikube, but if anyone would be interested in contributing one we'd be happy to look through a design proposal

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten