<p>I'm following an example from <a href="https://www.manning.com/books/kubernetes-in-action" rel="nofollow noreferrer">Kubernetes in Action</a> to run a simple docker image in kubernetes:</p>

<pre><code>$ bx login --apikey @apiKey.json -a  https://api.eu-de.bluemix.net
$ bx cs cluster-config my_kubernetes
$ export KUBECONFIG=..my_kubernetes.yml
</code></pre>

<p>Next, run the container:</p>

<pre><code>$ kubectl run kubia --image=luksa/kubia --port=8080 --generator=run/v1
$ kubectl expose rc kubia --type=LoadBalancer --name kubia-http
$ kubectl get service
$ kubectl get svc

NAME         CLUSTER-IP    EXTERNAL-IP   PORT(S)          AGE
kubernetes   10.10.10.1    &lt;none&gt;        443/TCP          20h
kubia-http   10.10.10.12   &lt;pending&gt;     8080:32373/TCP   0m
</code></pre>

<p>Fifteen minutes later ...</p>

<pre><code>NAME         CLUSTER-IP    EXTERNAL-IP   PORT(S)          AGE
kubernetes   10.10.10.1    &lt;none&gt;        443/TCP          20h
kubia-http   10.10.10.12   &lt;pending&gt;     8080:32373/TCP   15m
</code></pre>

<p>I don't have anything else running on the Kubernetes cluster.</p>

<p>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 - <a href="https://console.bluemix.net/docs/containers/cs_planning.html#cs_planning" rel="noreferrer">https://console.bluemix.net/docs/containers/cs_planning.html#cs_planning</a>.  </p>
