Can I set a Google Cloud Platform project quota at the organization or folder level?

user_15635544 0
Viewed 571

I am using Terraform to build a configuration to create a GCP project with all required infrastructure, which will be used to create non-production environments on a feature-by-feature basis.

I have reached a quota constraint for the limit BACKEND-SERVICES-per-project, which is set to 9 by default but we need 19. Manually requesting an increase through the GCP console form is fulfilled almost immediately however I want to run this as part of an automated pipeline.

Is there a way to request a quota increase at the organization or folder level which will then be applied to all new projects under that scope?

terraform-provider-gcp quota continuous-deployment google-cloud-platform
2 Answers

Unfortunately, you're not able to set project quota at the organization or folder level.

Please have a look at the documentation Working with quotas:

Google Cloud enforces quotas on resource usage for project owners, setting a limit on how much of a particular Google Cloud resource your project can use.

furthermore, at the section Managing your quota using the Cloud Console:

Depending on your resource usage, you may want to adjust your project's quota limits up or down.

All of your resources belongs to your projects and you can link them to your billing account only at the project level only. So, it should be expected that you can change quotas at the project level only.

You can try to change this behavior by filing a feature request at the Google Public Issue Tracker.

user_124287940

After contacting Google support with this question, we had the following answer:

Currently there is no process to increase the quota on the Organization/Folder level, neither is there anything that we can offer to override this "quota". The only possible solution that I can recommend right now would be for you to request a quota increase on the new projects manually.

To anyone with the same use-case, we created a pool of projects under a folder for which we manually requested (and were granted) the increase. We then used these projects as containers for the Terraform resources required to run the platform. This way, whenever we need a new feature environment, we provision the Terraform configuration and deploy the code to an available project from the pool. When the branch is merged, we terraform destroy the resources.

user_156355440
Related