Skip to Content

Run apps on their own servers

Add a node pool, let it grow and shrink, cap its price and reserve it for chosen apps.

Goal: a pool of servers in your cluster that only runs the apps you pick, such as a database or a GPU workload, and that adds servers when they are needed.

Before you start

  • A running cluster.
  • Credit on your balance for the extra servers. Some server types are rented for a fixed term; the price summary shows the commitment before you confirm. See Billing.

Add a pool

Open Infrastructure in the sidebar and select the cluster.

Select Add pool. The dialog walks through General, Machine, Placement, Storage, Extensions and Review.

General: a Pool name, such as db, and the Node count.

Machine: the node type. Every node in the pool uses the same one. Bare-metal and GPU servers are listed here too. Optional: Price caps, the most you accept to pay per node.

Placement: turn on Reserved pool so only apps that choose this pool run on it. Add Node labels if apps should find it by label.

Storage: the pool's role follows the storage type you pick here.

Check the price on Review and select Add pool.

The pool name and node type cannot change once the pool exists.

Move an app onto the pool

Open the app on the project canvas and go to its Settings tab.

Under Node pool, pick the pool. Any shared pool is the default.

Save. The app is redeployed onto the pool.

An app that keeps data on its nodes stays on its pool; the setting is locked for it.

Let the pool grow and shrink

Open the pool's Pool settings and go to Scaling.

Under Autoscaling, set the Minimum nodes and Maximum nodes.

Set when to add a node (Scale up CPU, Scale up memory) and when to remove one (Scale down CPU, Scale down memory). Turn off Allow scale down to keep the pool from shrinking.

Select Save autoscaling.

Cap the price

On the Scaling tab, Price caps set the most a new node of the pool may cost: Max hourly, Max monthly and Max setup fee. Select Save price caps.

Verify

  • The pool appears in the cluster with its nodes. A reserved pool shows Reserved; a normal one Shared.
  • The app's pods run on the pool's nodes after the redeploy.

Troubleshooting

  • The app stays pending after the move: the pool is full or has no nodes yet. Add nodes or raise Maximum nodes.
  • Other apps land on the pool: it is not reserved. Turn on Reserved pool on the Placement tab and select Save placement.
  • The pool does not grow: it is at Maximum nodes, the server type is out of stock in the region, or a new node would cost more than a price cap.

In IaC

Pools are listed in the cluster file; reserved: true and autoscaling go on the pool, and an app pins itself with pool: <name>. See Pools in IaC, reserved pools and pool autoscaling.

Next steps

On this page