<p>I have setup a new subnet in my shared VPC for GKE autopilot as the following:</p>
<pre><code>node ip: 10.11.1.0/24
first secondary ip: 10.11.2.0/24
second secondary ip: 10.11.3.0/24
</code></pre>
<p>I tried to test it by running simple nginx images with 30 replicas.</p>
<p>based on my understanding:</p>
<pre><code>I have 256 possible node IP
I have 256 possible pod IP
I have 256 possible service IP
</code></pre>
<p>after deploying, somehow my k8s are stuck with only 2 pods deployed and running. the rest is just in pending state with error code:<code>IP_SPACE_EXHAUSTED</code></p>
<p>my question is how come? I still have plenty IP address, this is fresh deployed kubernetes cluster.</p>

V Adhi Pragantha
<p>Pod CIDR ranges in Autopilot clusters</p>
<p>The default settings for Autopilot cluster CIDR sizes are as follows:</p>
<ul>
<li>Subnetwork range: /23</li>
<li>Secondary IP address range for Pods: /17</li>
<li>Secondary IP address range for Services: /22</li>
</ul>
<p>Autopilot has a maximum Pods per node of 32, you may check this <a href="https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr#cidr_settings_for_clusters" rel="nofollow noreferrer">link</a>.</p>
<p>Autopilot cluster maximum number of nodes is pre-configured and immutable, you may check this <a href="https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr#cidr_settings_for_clusters:%7E:text=The%20steps%20on%20this%20page%20do%20not%20apply%20to%20Autopilot%20clusters%20because%20the%20maximum%20number%20of%20nodes%20is%20pre%2Dconfigured%20and%20immutable." rel="nofollow noreferrer">link</a>.</p>
