1

I have deployed pods running nginx using helm, but when I do minikube service service_name, I see my service running on localhost as shown below. enter image description here

I thought that you need to access the service via the cluster IP not localhost?

I tried to access it using the cluster ip with the port of the service, but it doesn't seem to work.

I also tried to run it again after stopping docker, but it seems that docker is required to start the kubernetes cluster.

I'm following this kubecon demo , in the demo she can access it using the cluster ip just fine.

allen
  • 179
  • 3
  • 12
  • On MacOS incoming requests are expected on `localhost` and are then forwarded to the cluster IP address (if I'm not mistaken). – Tim Biegeleisen Jan 29 '21 at 09:00
  • In my opinion it is enaugh to start minikube with minikube start --vm=true PS. Remember to delete your cluster first. – Grunthor Jan 29 '21 at 09:21

2 Answers2

1

This is achieved using minikube tunnel command executed in separate terminal. This creates a tunnel and adds route to ClusterIP range.

Vasili Angapov
  • 8,061
  • 15
  • 31
1

It seems that the problem is the cluster was created using default docker driver.

Here's the thread that I found the solution, enter link description here

Just needed to start minikube cluster using virtualbox as the driver.

allen
  • 179
  • 3
  • 12