> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vegalake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clusters

> Configure VegaFlow execution sizing, lifecycle automation, status, and permissions.

# VegaFlow clusters

A cluster defines the execution capacity a QuickFlow uses. VegaFlow stores desired configuration and projects runtime status from the cluster orchestration layer; customer workflows use the VegaFlow API rather than the private control-plane API.

## Sizing rules

* **Node type** is required and must be selected from the customer-visible choices.
* **Minimum nodes** must be at least 1.
* **Maximum nodes** must be at least 1 and cannot be lower than minimum nodes.
* **Auto-scale** allows capacity to vary within the configured range.

Node-type administration and node-group mappings are platform-operator functions and are not part of the public API reference.

## Lifecycle settings

* **Auto-resume** permits a stopped cluster to become available when work needs it.
* **Auto-stop** permits idle shutdown.
* **Auto-stop time** must be positive when auto-stop is enabled.
* **Start** and **Stop** request explicit lifecycle transitions.

Status is a read-model projection and may take time to reflect an orchestration transition. Do not repeatedly submit conflicting lifecycle actions while a transition is in progress.

## Create a cluster

Choose a clear name, node type, minimum/maximum nodes, and lifecycle settings. Save the cluster, then wait for a usable status before starting the first QuickFlow run.

## Permissions

Collection permissions control listing and creation. Instance permissions control an individual cluster, including visibility and lifecycle actions. Grant QuickFlow operators only the cluster permissions their role requires.

## Troubleshooting

For a rejected model, check min/max ordering and the auto-stop time. For a cluster that does not become ready, check node type availability, capacity, status synchronization, and permission before editing the model.