It doesn’t look like you have cloud credentials set up to use Type=LoadBalancer. If it had worked, you’d see a “loadBalancerIP” field.
You could also expose this service as a NodePort, which is just a port in the 32xxx range that works on every machine in the cluster. You can then hook this up to a load balancer yourself, or just use the port directly. I find that NodePorts are great for testing since they work in all environment pretty easily. - Rob > On Jun 24, 2016, at 11:24 AM, Turgos <[email protected]> wrote: > > $ kubectl get svc api4docker > NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE > api4docker 10.3.0.95 8090/TCP 20m
