About resource pools
A resource pool is the capacity boundary for one or more applications. It combines CPU, memory, storage, and region into a single resource that applications can share.
Why pools matter
Applications need somewhere to run. Instead of purchasing capacity separately for every app, you create a pool and place compatible applications inside it. This makes shared capacity and cost easier to understand.
The pool list shows each pool’s name, region, capacity, status, and creation details. Open a pool for its overview, usage or metrics view, and settings that are currently available.
Pool status
| Status shown | Meaning | Recommended action |
|---|---|---|
| Pending / Provisioning | Creation is still in progress | Wait and refresh; do not create a duplicate immediately |
| Active | The pool is ready for applications | Select it during application deployment |
| Inactive | The pool is not currently available for normal workloads | Check the pool details and contact support if unexpected |
| Error / Failed | Creation or a later operation did not complete | Read the message, retry only when offered, or contact support |
Shared capacity
Each application receives a CPU and memory allocation from its selected pool. The sum of planned workloads should fit within pool limits, including room for traffic peaks and safe deployments.
Persistent volumes belong to application runtime configuration, while the pool supplies the overall storage capacity. Avoid allocating every last unit of capacity to normal traffic; leave headroom for growth and operational recovery.
Pool creation affects billing. Always review the displayed monthly estimate, currency, specifications, and region before selecting Create resource pool.
Naming pools
Choose names that help teammates identify intent, such as production-east, staging, or shared-services. Do not include account numbers, credentials, customer records, or other sensitive data.