<p>I am running a Kubernetes cluster with 3 master and 3 nodes.</p>

<p>I have found this to auto-scale worker nodes based on the pod's status.
<a href="https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/aws" rel="nofollow noreferrer">https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler/cloudprovider/aws</a></p>

<p>But, I couldn't find any blog or add-on to auto-scale master nodes.</p>

<p>Is there any reason to auto-scale master nodes, if yes how can we do that?</p>

<p>There is no need to <code>autoscale</code> the master nodes. In a practical world, your worker nodes responsibility is to run your work load and your master nodes responsibility is to make sure that your worker nodes are having desired state in the cluster.</p>

<p>Now all the end users will request your application (pods) and as the load increased they need to scale horizontally and more pods should be spawned. If the resources on worker nodes are insufficient to run those nodes, more worker nodes should be spawned.</p>

<p>In large cluster we do not run load on master node, but we need to make sure it is highly available so that there is no single point of failure to orchestrate the worker nodes. For that we can have 3 master multi-master cluster in place.</p>

<p>Worker nodes we worry about the <code>horizontal scalability</code> and In master node we worry about <code>high availability</code>.</p>

<p>But for building large cluster, you need to provide adequate resources to master nodes for handling the orchestration of load on worker nodes.</p>

<p>For more information on building large cluster, please refer official document:</p>

<p><a href="https://kubernetes.io/docs/setup/cluster-large/" rel="nofollow noreferrer">https://kubernetes.io/docs/setup/cluster-large/</a></p>

<p>In a nutshell, You can even have one master for 1000 worker nodes if you provide enough resources to that node. So, there is no reason to autoscale master comparing to the challenges we face in doing so. </p>
