<p>I have created the service with the following config file:</p>

<pre><code>{
   "kind":"Service",
   "apiVersion":"v1",
   "metadata":{
      "name":"my-service",
      "labels":{
         "app":"my-service"
      }
   },
   "spec":{
      "ports": [
         {
           "port":8080,
           "targetPort":"http-server"
         }
      ],
      "selector":{
         "app":"my-service"
      },
      "type": "LoadBalancer"
   }
}
</code></pre>

<p>Executed the following command:</p>

<pre><code>$ kubectl create -f my-service.json

            service "my-service" created
</code></pre>

<p>Then I want to see the external address of the service:</p>

<pre><code>$ kubectl get services
NAME             CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
my-service   10.0.203.169                 8080/TCP   3m
kubernetes       10.0.0.1       &lt;none&gt;        443/TCP    32m
</code></pre>

<p>In the examples of kubernetes apps it says there should be an "External IP" column, which is set:</p>

<pre><code>$ kubectl get services
NAME              CLUSTER_IP       EXTERNAL_IP       PORT(S)       SELECTOR               AGE
guestbook         10.0.217.218     146.148.81.8      3000/TCP      app=guestbook          1h
redis-master      10.0.136.3       &lt;none&gt;            6379/TCP      app=redis,role=master  1h
redis-slave       10.0.21.92       &lt;none&gt;            6379/TCP      app-redis,role=slave   1h
...
</code></pre>

<p>kubectl events shows no information about the load balancer and service.</p>

<p>What might be the problem?</p>

<p>I am using AWS if it helps.</p>

<p>Btw. If I look at the AWS console I can see the DNS name of the Load Balancer and connect to it.</p>

<p>It can take a few minutes for the external IP to show up because it takes a while for the cloud provider (EC2 in this case) to provision a load balancer for you.</p>

<p>On the off chance that it doesn't show up after a few minutes, run <code>kubectl get events</code> to see what's going wrong.</p>
