[Google Cloud Run] Unable to create 0 instances because there are already 0 in this region

[andrefedev]

I am creating a scale to 0 google cloud run instance and I am getting the following error: Unable to create 0 instances for "apigo-dev-00002-zeg" because there are already 0 in this region. The strange thing is that according to quotas I have only used 25% of the region's cpu. I also noticed that the instance was running normally and a new revision caused the problem. Now I have created a new test instance and it also gives me the same error.

[drm80]

I get the same error when trying to deploy a new revision of a GCP function. The problem is related to a specific region (in my case europe-west3). Deploying the function in another region works without any problems. 

[Maxpain]

The same problem in europe-north1 region

[albertoabruzzo]

@andrefedev @Maxpain @drm80  Did you solved the issue? I have the same problem with different projects!

[andrefedev]

@albertoabruzzo @Maxpain 

The reason why you are encountering this error [1] is that you are trying to deploy a Cloud Run revision with too high of value of your max instance or you are exceeding the quota limit of your max instance which is 10.  For now you can request to increase the quota.

Then you have two options. 1). Increase the quota. 2). Set manual settings like --max-instances=5 and suddenly it worked, by default that value is 10.

[albertoabruzzo]

we deploy from cloud build, already setted max-instances on the cloud console to 1 but nothing changes

[andrefedev]

My instances will also be deployed with cloud build. The default limit of instances per region is 10. Try to create a new instance manually, use the sample container. So all you have to do is set the max-instances field to 1 and check if this works.

Also check the other services that are running, in my case there was a service that had max-instances of 100. I had to delete it manually.

[jvumex]

Someone find any solution for this?

When I change the region to central, the service works, but in us-west all new deploys in any service broke

[albertoabruzzo]

Open a ticket and write also here https://issuetracker.google.com/issues/278096734