title: kubeadm init on CentOS 7 using AWS as cloud provider enters a deadlock state
body: <p>I am trying to install Kubernetes 1.4 on a CentOS 7 cluster on AWS (the same happens with Ubuntu 16.04, though) using the new <code>kubeadm</code> tool.</p>
  
  <p>Here's the output of the command <code>kubeadm init --cloud-provider aws</code> on the master node:</p>
  
  <pre><code># kubeadm init --cloud-provider aws
  
  &lt;cmd/init&gt; cloud provider "aws" initialized for the control plane. Remember to set the same cloud provider flag on the kubelet.
  &lt;master/tokens&gt; generated token: "980532.888de26b1ef9caa3"
  &lt;master/pki&gt; created keys and certificates in "/etc/kubernetes/pki"
  &lt;util/kubeconfig&gt; created "/etc/kubernetes/kubelet.conf"
  &lt;util/kubeconfig&gt; created "/etc/kubernetes/admin.conf"
  &lt;master/apiclient&gt; created API client configuration
  &lt;master/apiclient&gt; created API client, waiting for the control plane to become ready
  </code></pre>
  
  <p>The issue is that the control plane does not become ready and the command seems to enter a deadlock state. I also noticed that if the <code>--cloud-provider</code> flag is not provided, pulling images from Amazon EC2 Container Registry does not work, and when creating a service with type <code>LoadBalancer</code> an Elastic Load Balancer is not created.</p>
  
  <p>Has anyone run <code>kubeadm</code> using <code>aws</code> as cloud provider?</p>
  
  <p>Let me know if any further information is needed.</p>
  
  <p>Thanks! </p>