<p>We are attempting to make several private Kubernetes clusters. We can find limited documentation on specific settings for the private cluster, therefore we are running into issues related to the subnetwork IP ranges. </p>

<p>Say we have 3 clusters: We set the Master Address Range to 172.16.0.0/28, 172.16.0.16/28 and 172.16.0.32/28 respectively.</p>

<p>We leave Network and Subnet set to "default". We are able to create 2 clusters that way, however, upon spin-up of the 3rd cluster, we receive the error of "Google Compute Engine: Exceeded maximum supported number of secondary ranges per subnetwork: 5." We suspect that we are setting up the subnetwork IP ranges incorrectly, but we are not sure what we are doing wrong, or why there is more than 1 secondary range per subnetwork, to begin with. </p>

<p>Here is a screenshot of the configuration for one of the clusters:
<a href="https://i.stack.imgur.com/Tlp5Z.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Tlp5Z.png" alt="kubernetes configuration screenshot"></a></p>

<p>We are setting these clusters up through the UI.</p>

<p>This cluster has VPC-native (alias IP) enabled, which use 2 secondary ranges per cluster.</p>

<p>See <a href="https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips#secondary_ranges" rel="nofollow noreferrer">https://cloud.google.com/kubernetes-engine/docs/how-to/alias-ips#secondary_ranges</a></p>

<p>According to </p>

<p><code>Google Compute Engine: Exceeded maximum supported number of secondary ranges per subnetwork: 5.</code></p>

<p>the max is 5. That's why the 3rd one failed to create.</p>
