Skip to main content
A destination tells Arklow where work should go. A capacity pool tells Arklow what that destination depends on. Every destination belongs to a pool. A new destination begins in a standalone pool of its own. If several destinations draw from the same set of containers, GPU cluster, model deployment, or provider quota, you can place them in one shared pool.

​
Standalone and shared pools

A standalone pool keeps one destination’s capacity separate from every other destination. This is the right default when a destination has its own scaling boundary. A shared pool represents one physical supply of capacity behind several destinations. When that supply is constrained, Arklow evaluates demand from every member against their shared capacity. A destination belongs to one pool for each resource its work draws from. Add it to a pool only when it competes for that pool’s resource. Similar work, shared ownership, or matching labels are not enough on their own.
Adding a destination to a pool declares that pressure and capacity are shared. A destination that does not draw from the pool’s resource can wait for a constraint that has nothing to do with its work.

​
Pool allocation

Arklow continues to control each lane locally. A shared pool adds a second boundary across the destinations and lanes drawing from the same capacity. When the pool is steady, active work can use capacity that other lanes do not need. When the pool is constrained, Arklow can hold excess work from a noisy contributor while preserving room for other active lanes. Admission follows the tighter of the lane’s local limit and its tightest current share across its pools.

​
Create a shared pool

1

Open a destination

Go to Destinations and open one of the destinations that uses the shared capacity.
2

Join a pool

Under Pooling, select the pool for the resource this destination draws from. A destination’s own standalone pool appears in the list, so you can join a destination that has no shared pool yet.
3

Confirm the change

Review the destinations that will share pressure and capacity, then confirm. The destination keeps its other pools.
4

Add the remaining members

Open the pool to add or remove the other destinations that draw from its resource.
Removing a destination from a pool removes only that membership. A destination removed from its last pool gets a new standalone pool. You can remove the last destination from a pool that still has scale targets. The pool’s pressure clears and its targets settle to their minimum replicas. The pool remains, so you can add members again, or delete it once no scale targets are attached.

Scale targets

Connect a pool to infrastructure that can change its real supply of capacity.