<p>I followed <a href="http://kubernetes.io/docs/getting-started-guides/aws/" rel="nofollow">the tutorial</a> how to create a k8s cluster on aws using ubuntu. This works great, so I have one master and three nodes - minions. However I haven't found any working working recipe how to add a new node to the cluster.</p>

<ol>
<li>First of all, I have a new autoscaling group in aws. It was created along with the cluster. I tried to increase the number of nodes in the scaling group, the scaling procedure really added an instance but the node <em>is not among the k8s cluster</em>. There is no kubelet, kube-proxy, no such thing on the instance. So, it's reasonable that it did not join the k8s cluster.</li>
</ol>

<p>As I have not found any tutorial, maybe I need to do some manual procedure. But it would be weird autoscaling. What am I supposed to do? kube scripts install the cluster, add scaling group and it does not work?</p>

<ol start="2">
<li>I do not insist on the automatic scaling, I just need to add a new node in the case of any failure or how we will add new running pods/rcs. I found a reference in <a href="http://blog.kubernetes.io/2016/03/building-highly-available-applications-using-Kubernetes-new-multi-zone-clusters-a.k.a-Ubernetes-Lite.html" rel="nofollow">this article</a> in the section called <code>Add more nodes in a second zone</code>, note that this is about multizone deployment.</li>
</ol>

<p>So I tried things like:</p>

<p><code>KUBE_USE_EXISTING_MASTER=true KUBERNETES_PROVIDER=aws KUBE_AWS_ZONE=eu-central-1b NUM_NODES=1 KUBE_SUBNET_CIDR=172.20.1.0/24 MASTER_INTERNAL_IP=172.20.0.9 kubernetes/cluster/kube-up.sh</code> </p>

<p>but it always failed with:</p>

<p><code>A client error (AlreadyExists) occurred when calling the CreateLaunchConfiguration operation: Launch Configuration by this name already exists - A launch configuration already exists with the name kubernetes-minion-group-eu-central-1b</code></p>

<p>There must be definitely some way how to do that, can you please someone help me? Thank you!</p>

<p>After some attempts it seemed that the auto-scaling group worked using debian images. Note that it needs aprox. 2 minutes once the instance is ready with all installed necessities and you can see the instance using <code>get nodes</code>.</p>
