<p>I'm looking for a way to increase the master node VM size on GKE.</p>

<p>On <a href="https://kubernetes.io/docs/admin/cluster-large/#size-of-master-and-master-components" rel="noreferrer">https://kubernetes.io/docs/admin/cluster-large/#size-of-master-and-master-components</a> it suggests that for a cluster of 11-100 nodes we should be using an n1-standard-4 VM for Kubernetes master. </p>

<p>However, since the cluster has started out smaller, and since grown to this size, does that mean that we're stuck with an underpowered master node? From the above link:</p>

<blockquote>
  <p>Note that these master node sizes are currently only set at cluster startup time, and are not adjusted if you later scale your cluster up or down (e.g. manually removing or adding nodes, or using a cluster autoscaler)"</p>
</blockquote>

<p>So, is there any way to increase the size of the master?</p>

<blockquote>
  <p>The Kubernetes documentation that you pointed out is <strong>NOT</strong> correct and should be modified since the master actually scales. </p>
</blockquote>

<p>First of all notice that how and when Google Cloud takes care of resizing the master should not be a concern for users if the behaviour of the cluster is stable and performant. </p>

<p>It is a managed service and therefore some details are not public, for example how the master is resized and which algorithms are used are not shared.</p>

<p>Moreover there is no information or disclaimer regarding the machine type of the master in the autoscaler GKE <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler" rel="noreferrer">official documentation</a> and it if the master was not able to resize since it would have been an action potentially disruptive for the cluster health.</p>

<h2>From the blog</h2>

<p>"Master VM is automatically scaled, upgraded, backed up and secured"</p>

<ul>
<li><a href="https://cloudplatform.googleblog.com/2017/11/Cutting-Cluster-Management-Fees-on-Google-Kubernetes-Engine.html" rel="noreferrer">https://cloudplatform.googleblog.com/2017/11/Cutting-Cluster-Management-Fees-on-Google-Kubernetes-Engine.html</a></li>
</ul>

<hr>

<p>However if you want you can test the behavior:</p>

<ul>
<li><p>Create a cluster having one node</p></li>
<li><p>Add 10 nodes</p></li>
<li><p>The master will be not reachable for a moment and a call to the API will resolve in an error</p>

<pre><code>   $ gcloud container clusters get-credentials cluster-1 --zone us-central1-a --project **-**
   Fetching cluster endpoint and auth data.
   WARNING: cluster cluster-1 is not running. The kubernetes API may not be available.
</code></pre></li>
<li><p>Inspect the logs, you will notice that in the logs will be present an entry "master upgrade"</p></li>
</ul>

<hr>

<p>There is an <a href="https://issuetracker.google.com/79973484" rel="noreferrer">feature request</a> asking to Improve the Google cloud documentation, you can decide to star it in order to receive updates.</p>

<p>On the other hand to fix the Kubernetes documentation I opened a <a href="https://github.com/kubernetes/website/issues/8640" rel="noreferrer">public issue</a> on Github.</p>
