- The required allocations fit into your free quotas.
- The subnet you select during cluster creation has enough free CIDR blocks.
If you use a default subnet, it already meets the CIDR block requirement. If you plan to use a non-default subnet, check that the subnet has the necessary IP address allocations available.
Private IP address allocations
For the control plane:-
5
/32allocations:- 1 for the internal load balancer.
- 4 for the control plane instances in case of high availability (3 for
etcdinstances and 1 more to enable control plane updates). If control plane high availability is disabled, 3/32allocations are enough.
-
1 allocation for Kubernetes services. By default, a
/16CIDR block is allocated, but you can set thespec.kube_network.service_cidrsparameter during cluster creation to specify a custom CIDR block, in range from/12to/28.
- 1
/24allocation for Pods assigned to a node. - 1
/32allocation for the internal IP address of a node.
Public IP address allocations
The public IP address of the cluster is allocated automatically from the Managed Kubernetes project and does not use up your quota. If you have enabled public IP addresses for nodes in a node group (with thespec.template.network_interfaces.public_ip_address parameter), you need 1 /32 public IP allocation for each node.
To assign public IP addresses from a fixed set, create a subnet with a dedicated public IP address pool and configure the node group to use it. Individual node IP addresses may change, but they are selected from the subnet’s pool.