# Understanding CubeCOS Node Roles

> Learn the responsibilities and functions of each CubeCOS node role within the cluster architecture.

## CubeCOS node roles overview {#cubecos-node-roles-overview}

Each CubeCOS cluster defines distinct node roles you can combine or separate based on deployment requirements and performance goals.

The diagram below illustrates the function of each node type, helping you plan resource allocation and build a scalable infrastructure.

  

### Compute node {#compute-node}

A compute node provides processing power to run virtual machines, containers, and other workloads. It must rely on the cluster's shared storage.

- Delivers CPU and memory resources for workloads
- Connects to shared storage provided by storage-capable nodes
- Suitable for deployments where compute and storage scale independently

### Compute with storage node {#compute-with-storage-node}

This node type contributes both compute and storage resources to the cluster. It supports horizontal scaling by combining workload execution and data storage on a single node.

- Adds CPU, memory, and storage capacity
- Supports balanced resource scaling
- Recommended for clusters with high density requirements

### Control node {#control-node}

A control node runs the CubeCOS control plane components, including the web-based dashboard and system management services (Infrascope). In HCI or web scale deployments isolating the control plane on dedicated nodes improves responsiveness and resilience.

- Hosts orchestration, cluster management, and UI services
- Enhances control plane performance in large-scale deployments (HCI or web scale)
- Recommended for clusters with high API and management traffic

### Control-converged node (AIO) {#control-converged-node-aio}

A control-converged node combines compute, storage, networking, and control plane functions into a single system. This design is optimized for small-scale or space-constrained environments.

- Delivers a complete hyperconverged platform in one node
- Includes the CubeCOS dashboard and control plane services
- Ideal for branch offices, SMBs, and All-In-One scenarios

### Storage node {#storage-node}

A storage node provides dedicated storage capacity to the cluster without contributing compute resources, optimized for high-throughput and storage-intensive workloads.

- Adds flash or HDD-based storage capacity to the cluster
- Supports storage-heavy workloads
- Scales storage independently of compute resources

## Specialized CubeCOS node roles {#specialized-cubecos-node-roles}

### Edge-Core node {#edge-core-node}

Edge-core nodes provide an integrated Kubernetes platform optimized for lightweight, remote edge environments on minimal hardware.

- Lightweight footprint ideal for remote and edge deployments
- Integrated Kubernetes service for edge computing workloads
- Deployed in a 2 edge-core nodes + 1 moderator configuration

### Moderator node {#moderator-node}

A Moderator node acts as a quorum witness in the lightweight 2 edge-core node +1 moderator cluster deployments. It does not run compute or storage workloads but serves to ensure cluster quorum for high availability.

- Maintains quorum for HA in 2+1 topologies
- Minimal resource footprint
- Essential for small-scale edge deployments