docker for mac kubernetes use ip other than localhost

But why is this closed It surely does not work in the latest greatest Docker desktop.

Via the OSX Launchpad, launch the edge whale, reset your world, and in the preferences window, turn on Kubernetes support.

Both lines will have a second (host) TCP port number as well, in the low 30000s.

Copy and paste one of them and run e.g.

This is the thing I most expect to work, but you will get a connection refused.

Within the cluster, normal paths to reach between services work fine.

Within this shell, run wget, where again this is the second port number from either service.

The service layer seems to be unusable from the mac host, be it via ClusterIP, NodePort, or LoadBalancer.

This workaround doesnt address how youd hit a deployment with more than 1 pod (i.e.

IWe could just be using slightly malformed service definitions for this use case.

As a workaround, one need to expose it manually with the below command as shown under.

That means you cant run anything on the same port on the host you cant have Postgres running on the host and under Kubernetes if they have the same port.

In fact, by binding to everything it also bypasses the Mac firewall (see issue 729 ), allowing anyone to connect to exposed LoadBalancer IPs.

The np port displayed as opened by the service is exposed though.

I would expect NodePort to do the same thing in kubernetes-on-docker, but it doesnt seem to work.

Ideally, though, there would be routed networking between service IPs and the localhost interface, just like there is on other OS-es.

So far, the experience with Docker Desktop as starter has been awful.

I noticed that for some reason the deployment came up with ClusterIP.

You want NodePort.

Change the deployment to use that in the yaml.

Using ClusterIP obviously it is available only within the cluster.

This issue can happen if you deploy without a deployment yaml file as I did.

So I uninstalled minikube on the other machine using the steps kubernetesminikube1043 (comment).

The other observation is that the status of Kubernetes on the machine that is not working is showing Kubernetes is starting permanently.

The only solution that worked for me is to reset to factory defaults, since restart, reset kubernetes cluster, reset disk image options are not working.

Docker For Mac Kubernetes Use Ip Other Than Localhost