The Kubernetes server runs locally within the Docker instance, is not configurable, and is a single-node cluster. This includes a standalone Kubernetes server and client, as well as Docker CLI integration. That can be far more convenient if you have a lot of Services to expose, but it would likely be too big of a headache to set up just for one or two of them. Kubernetes is available in Docker for Mac 17.12 CE Edge and higher, and 18.06 Stable and higher. The other way you can chose to do things is run an in-cluster Ingress controller, such as ingress-nginx, and use virtual-hosting to expose all your services on just one port.

Or you can skip the pretense and create the Service legitimately of type: NodePort, and then you and kubernetes will be on the same page about what is happening. It's unclear whether you can just use that NodePort-ish port as-is, or whether the Service in 'pending' state somehow means traffic will not route as expected. That said, one can see from your output that kubernetes has behaved as if it was type: NodePort (with your specific example showing that port 32670 goes to port 8080 on your Service). Unless something seriously magical has happened with 'Docker for Mac,' then the type: LoadBalancer is only designed for a cloud environment, where the Ingress controller can provision a cloud load balancer (i.e.

Install docker for mac edge