The new default Service IP will be assigned starting July 2023.
| With the new default Service IP range you'll save on network range quotas because we won't create a new Service secondary range. Hello Tee, We are writing to let you know that GKE Autopilot and Standard clusters will have a new default Service IP range assignment starting in July 2023. What do you need to know? We are providing a new default Service range for GKE Autopilot and Standard clusters. This update will let you free up more of your private IP space and relieve your Google Cloud network quota for subnet ranges. Review the table below to visualize the update. Current default GKE Service IP range | New default GKE Service IP range | Picked from the 10.0.0.0/8 range during cluster creation. | Assigned the 34.118.224.0/20 range during cluster creation. | The new IP range will be used if you do not specify the --services-ipv4-cidr or the --services-secondary-range-name during GKE Autopilot or GKE Standard cluster creation. What's changing? - The GKE Service IP range will be allocated from the reserved Google public IP pool 34.118.224.0/20 and used on newly-created clusters. Existing clusters will not be affected by this change.
- You'll save on network range quotas since we won't create a new Service secondary range.
- You won't need to account for a CIDR assignment for the Service range, hence you'll be saving IP addresses and IP management overhead.
The changes will be effective as follows: - GKE Autopilot starting in July 2023.
- GKE Standard starting in August 2023.
What do you need to do? No action is required from you. However, we recommend reviewing your DNS configurations to ensure that your GKE Services are not assumed to be in the 10.0.0.0/8 IP address range. If you do not wish to leverage this new default feature, please indicate the --services-ipv4-cidr or the --services-secondary-range-name during cluster creation. We're here to help - Please refer to the Google Cloud page on planning IP allotment for further clarification on IP requirements for GKE clusters to consider.
- If you have any questions, please contact your account manager.
Thanks for choosing Google Kubernetes Engine. | | | | —The Google Kubernetes Engine Team | | | | |