Kubernetes service external IP address remains pending with IBM Cloud (earlier called as Bluemix)
To close out the thread here, LoadBalancer cannot be used in a lite (aka free) cluster tier. The differences between lite and standard clusters can be found here - https://console.bluemix.net/docs/containers/cs_planning.html#cs_planning.
Run the following to determine if there are any failure events.
kubectl describe svc kubia-http
Thanks to Chris Rosen's answer, I was able to find a workaround:
$ bx cs workers my_kubernetesOKID Public IP Private IP Machine Type State Statuskube-par01-xxxxx 1.2.3.4 6.7.8.9 free normal ReadyNote the Public IP address: 1.2.3.4
Expose the service with NodePort:
$ kubectl expose rc kubia --type=NodePort --name kubia-http2Check the NodePort details:
$ kubectl get svcNAME CLUSTER-IP EXTERNAL-IP PORT(S) AGEkubernetes 10.10.10.1 <none> 443/TCP 21hkubia-http2 10.10.10.193 <nodes> 8080:31247/TCP 10sAccess the service using the exposed port on the worker Public IP address:
$ curl http://1.2.3.4:31247/You've hit kubia-bjb59