Database storage auto-scaling Innovation Release
- Hybrid Manager dual release strategy
- Documentation for the current Long-term support release
Database storage auto-scaling monitors the storage utilization of your cluster's data volumes. When usage exceeds a configured threshold, HM automatically expands the underlying PersistentVolumeClaim (PVC) — keeping your databases online and preventing outages caused by disk full events.
You configure the trigger threshold, the scaling method (fixed amount or percentage), and a maximum disk size to prevent runaway growth. Expansion is performed as an online operation (if your storage driver supports it), so your Postgres database remains accessible throughout.
Note
Database storage auto-scaling applies to the primary data volume only. If your cluster uses separate WAL volumes, the WAL volume is not in scope. Backup storage is also not affected.
Automations are configured per cluster, and — for clusters with multiple locations such as replica clusters or PGD clusters with multiple data groups — you must configure the automation separately for each replica cluster or data group.
Database storage auto-scaling parameters
When you configure an automated operation, there are specific parameters for the database storage auto-scaling automation in addition to the general automation fields:
| Field | Description |
|---|---|
| Disk Threshold | The disk utilization percentage that triggers a scaling event (for example, 80). |
| Scaling Method | Choose how to increase the disk size: Scale by Quantity adds a fixed size each time (for example, 10Gi, 50Gi); Scale by Percentage increases by a percentage of the current capacity (for example, 20%). |
| Maximum Disk Size | The upper limit for scaling. The automation stops expanding once this size is reached, preventing runaway growth. |
| Maintenance Window | If your storage driver supports online expansion — meaning the operation causes no downtime — you can leave the maintenance window field empty and the task will execute as soon as the threshold is crossed. |
Once active, HM evaluates disk utilization at each interval. When the threshold is crossed, a task is created in Task Manager. You can monitor task status — pending, completed, or rejected — from either the cluster-level Task Manager tab or the project-level Task Manager in the left navigation.
- On this page
- Database storage auto-scaling parameters