Skip to content

broker-pool/allocate

Use allocate (vs add) when getting machines from source pool

Controls how the Pool Broker moves machines between pools when a cluster is created.

If false (default), the broker uses the drpcli pools manage add/remove methods. A per-cluster pool is created whose ParentPool is broker-pool/pool, and machines are moved into that per-cluster pool on create. On destroy, each machine is popped off its broker-pool/pool-stack and returned to its previous pool (which may be a different cluster's pool, for chained Pool Broker use). This matches the Context Broker behavior and produces one visible pool per cluster.

If true, the broker uses drpcli pools manage allocate/release: machines remain in the shared broker-pool/pool for the lifetime of the cluster and no per-cluster pool is created. Use this when multiple clusters must draw from a single shared pool without fragmenting it.

Default was changed from true to false in v4.16 to align Pool Broker with Context Broker (see rackn/product-backlog#785). To preserve pre-v4.16 behavior on an existing fleet, set broker-pool/allocate: true on the Pool Broker machine or its profile before upgrading.

Objects that Reference broker-pool/allocate

Objects used by broker-pool/allocate

Not used in current content packs