<p>We have an use case where we run pods with hostNetwork set to true, and these pods will be deployed in a dedicated node pool where maxPodRange is set to 32. To avoid IP wastage we are trying to understand if there is a way to override this maxPodRange constraint, so that the kube-scheduler will not restrict us with 32 pods during deployment. Please let me know if you have come across any solution or workaround. Thanks in advance!</p>

Jay
<p>For autopilot cluster 32 is the max and this restriction cannot be bypass. You can use up to 256 IPs for non-autopilot cluster. Checkout the limits <a href="https://cloud.google.com/kubernetes-engine/quotas#limits_per_cluster" rel="nofollow noreferrer">here</a> and how to configure <a href="https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr#setting_the_maximum_number_of_pods_in_a_new_node_pool_for_an_existing_cluster" rel="nofollow noreferrer">here</a>.</p>
