<p>Tried installing kubernetes v1.2.0 on azure environment but after installation cannot access kube apis at port 8080.</p>

<p>Following services are running :</p>

<pre><code>root      1473  0.2  0.5 536192 42812 ?        Ssl  09:22   0:00 /home/weave/weaver --port 6783 --name 22:95:7a:6e:30:ed --nickname kube-00 --datapath datapath --ipalloc-range 10.32.0.0/12 --dns-effective-listen-address 172.17.42.1 --dns-listen-address 172.17.42.1:53 --http-addr 127.0.0.1:6784
root      1904  0.1  0.2  30320 20112 ?        Ssl  09:22   0:00 /opt/kubernetes/server/bin/kube-proxy --master=http://kube-00:8080 --logtostderr=true

root      1907  0.0  0.0  14016  2968 ?        Ss   09:22   0:00 /bin/bash -c until /opt/kubernetes/server/bin/kubectl create -f /etc/kubernetes/addons/; do sleep 2; done
root      1914  0.2  0.3  35888 22212 ?        Ssl  09:22   0:00 /opt/kubernetes/server/bin/kube-scheduler --logtostderr=true --master=127.0.0.1:8080
root      3129  2.2  0.3  42488 25192 ?        Ssl  09:27   0:00 /opt/kubernetes/server/bin/kube-controller-manager --master=127.0.0.1:8080 --logtostderr=true
</code></pre>

<p><code>curl -v http://localhost:8080</code> returns error</p>

<blockquote>
  <ul>
  <li>Rebuilt URL to: <a href="http://localhost:8080/" rel="nofollow">http://localhost:8080/</a></li>
  <li>Trying 127.0.0.1...</li>
  <li>connect to 127.0.0.1 port 8080 failed: Connection refused</li>
  <li>Failed to connect to localhost port 8080: Connection refused</li>
  <li>Closing connection 0 curl: (7) Failed to connect to localhost port 8080: Connection refused</li>
  </ul>
</blockquote>

<p>Same works fine with <code>v1.1.2</code>.</p>

<p>I'm using following guidelines <a href="https://github.com/kubernetes/kubernetes/tree/master/docs/getting-started-guides/coreos/azure" rel="nofollow">https://github.com/kubernetes/kubernetes/tree/master/docs/getting-started-guides/coreos/azure</a> and updated line <a href="https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml#L187" rel="nofollow">https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml#L187</a> to user version <code>v1.2.0</code>.</p>

<p>The services you show running do not include the apiserver. For a quick breakdown I can explain what each service does that you show running.</p>

<ul>
<li><a href="https://www.weave.works/" rel="nofollow">Weave</a>: This is a software overlay network and assigns IP addresses to your pods.</li>
<li><a href="http://kubernetes.io/docs/admin/kube-proxy/" rel="nofollow">kube-proxy</a>: This runs on your worker nodes allow pods to run and route traffic between exposed services.</li>
<li><a href="http://kubernetes.io/docs/user-guide/kubectl-overview/" rel="nofollow">kubectl create</a>: Kubectl is actually the management cli tool but in this case using <code>-f /etc/kubernetes/addons/; sleep 2</code> is watching the /etc/kubernetes/addons/ folder and automatically creating any objects (pods, replication controllers, services, etc.) that are put in that folder.</li>
<li><a href="http://kubernetes.io/docs/admin/kube-scheduler/" rel="nofollow">kube-scheduler</a>: Responsible for scheduling pods onto nodes. Uses policies and rules.
<a href="http://kubernetes.io/docs/admin/kube-controller-manager/" rel="nofollow">kube-controller-manager</a>: Manages the state of the cluster by always making sure the current state and desired state are the same. This includes starting/stopping pods and creating objects (services, replication-controllers, etc) that do not yet exist or killing them if they shouldn't exist.</li>
</ul>

<hr>

<p>All of these services interact with the <a href="http://kubernetes.io/docs/admin/kube-apiserver/" rel="nofollow">kube-apiserver</a> which should be a separate service that coordinates all of the information these other services use. You'll need the apiserver running in order for all of the other components to do their jobs.</p>

<p>I won't go into the details of getting it running in your environment but from it looks like in the comments on your original thread you found some missing documentation to get it running.</p>
