The default quotas on a new GCP subscription are not sufficient for a typical production level VMware Tanzu Operations Manager deployment. This topic lists the quotas that you need for a typical Tanzu Operations Manager deployment.
For a single Tanzu Operations Manager deployment, ensure that you have the following quotas.
| Metric | Resource | Suggested minimum quota |
|---|---|---|
| CPUs | Regional | 150* |
| Firewall rules | Global | 15 |
| Forwarding rules | Global | 15 |
| Backend services | Global | 5 |
| Health checks | Global | 5 |
| Images | Global | 10 |
| Static IP addresses** | Regional | 5 |
| In-use IP addresses | Global | 5 |
| In-use IP addresses** | Regional | 5 |
| Networks | Global | 5 |
| Subnetworks | Global | 5 |
| Routes | Global | 20 |
| Target pools | Global | 5 |
| Target HTTP proxies | Global | 5 |
| Target HTTPS proxies | Global | 5 |
| Persistent disk standard (GB) | Regional | 15,000 |
* Assuming a deployment with 100 app instances.
** Assuming a SNAT topology.
To view production-level deployment options for Tanzu Operations Manager on GCP, see the Reference architecture for Tanzu Operations Manager on GCP.
For instructions about setting up the GCP resources required to deploy Tanzu Operations Manager, see Preparing to deploy Tanzu Operations Manager on GCP.
