You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After August 1, 2023, you'll see the following changes for SKUs related to Cloud Load Balancing:
We’ll remove the SKUs from their existing Compute Engine product category and create new SKUs in the Networking category.
For all load balancer types:
We’re creating new SKUs for forwarding rules under the Networking category. These new SKUs apply to the forwarding rule minimum and additional charges. Currently, forwarding rule SKUs are in the Compute Engine category.
We’ll split inbound data processing for the three regions that make up the Americas group (us-central1, us-east1, and us-west1) into separate SKUs for each region.
For internal HTTP(S) load balancing:
For consistency with other load balancers, we’re splitting the data processing SKUs into separate inbound and outbound SKUs. Currently, these are grouped into a single SKU (for both inbound and outbound data processing) per region.
We’ll split proxy instance SKUs for the three regions that make up the Americas group (us-central1, us-east1, and us-west1) into separate SKUs for each region.
For internal TCP/UDP load balancing, there is a one to one mapping between the new SKU IDs in the Networking category to the current SKU IDs in the Compute Engine category.
For global external HTTP(S) load balancers, external TCP/SSL proxy load balancers and network load balancers, we're splitting inbound data processing into separate SKUs for each load balancer type. Currently, inbound data processing is grouped into a single SKU per region for all of these load balancers.
I will therefore remove Load Balancer from this calculator. Anyone who wants to deal with the new pricing is welcome to put it in.
The text was updated successfully, but these errors were encountered:
Google has written and announced:
I will therefore remove Load Balancer from this calculator. Anyone who wants to deal with the new pricing is welcome to put it in.
The text was updated successfully, but these errors were encountered: