Guidance for Google Cloud Function Quota Deprecations

[Hendrik Schalekamp]

On the Google Cloud Functions Quota Page  many of the quotas are marked as deprecated. E.g. "CPU allocation in function invocations (deprecated)".

1. What have these quotas been replaced with?
2. How do I change over to whatever the new quota system is?
3. Where do I find documentation about the deprecation?

Kind regards

[Mohammad I (Cloud Platform Support)]

Hello Hendrik,

The issue seems to be known to the Cloud Functions Engineering team. It appears customer's have been notified via e-mail regarding this issue of removing Google Cloud Functions Quotas on September 8, 2020. You should see further details on this in your email. 

Some users may have used quotas as a way to limit spending, e.g., either via the default quota limits or by lowering their quota. They should now use Cloud Billing Budgets or Max Instances to limit spending or usage.

Cloud functions Engineering team has removed the following quotas:

• MiByMilliSeconds

• HttpRequestData

• HttpResponseData

• DNSResolutions

• NetworkIngress (All Regions)

• SocketConnect (All Regions)

• NetworkEgress (All Regions)

• FunctionCalls (All Regions)

• CPUMilliSeconds (All Regions)

• CPUMilliSecondsDaily

They are also removing the following per user quotas:

• Read

• Write

• TestCall

Please note that Cloud Functions Engineering team has not removed any nonbillable quotas. You can fine all the quotas of Cloud Functions here.