Skip to main content
Talos Director is in Limited Availability. Limited Availability customers receive full production support and work directly with Sidero Labs engineering during onboarding. General availability is planned for January 2027, and the console is changing quickly until then, so details on these pages may differ from what you see.To request access, visit siderolabs.com/getdirector.
Storage pools are the shared datastores that back virtual machine disks in Talos Director. Because storage is a shared dependency for VM runtime, live migration, High Availability (HA), and capacity planning, the Storage Pools pages make pool state visible directly — before a degraded or unmounted pool surfaces as a VM failure. Use the Storage Pools page to answer capacity and health questions across every cluster, then open an individual pool to inspect its host mounts, the virtual machines that depend on it, and its file-level contents.
Storage Pools is part of the wider Storage area under Compute, alongside Storage Policies, Compliance, Recommendations, and Capabilities. This page covers pools; the related pages govern how disks are placed on them.

The Storage Pools view

Navigate to Compute > Storage > Storage Pools (/storage-pools) to see every pool across all clusters in one table.

Columns

The table shows the following columns.

Controls

The controls above the table let you search, shape, and export the view:
  • Filter storage pools… — narrow the table with free text or query-style expressions, for example type:nfs.
  • Columns — choose which columns are visible.
  • Export CSV — download the current view for reporting or offline analysis.
  • Refresh — reload pool data on demand.
  • Add Storage Pool — register a new pool and make it available to a cluster.
  • Global search — the top-bar search spans VMs, hosts, networks, and users, and supports scoped queries such as vm:name.

Add a storage pool

Select Add Storage Pool to register a new pool. Complete the following fields.

The storage pool detail screen

Click a pool name to open its detail screen. The header identifies the pool, its backing type (for example, NFS storage pool), and its current state, with a Back to storage pools link and an Actions menu for pool-level operations. Three tabs organize the pool’s information.

Overview

The landing tab summarizes the pool’s identity, capacity, and mount health: Check Host Mounts first when troubleshooting. Every host in the cluster should show the pool as mounted with compliant options — a host that has lost its mount, or mounts the pool with non-standard options, can strand or degrade the VMs placed on it. The compliance column surfaces this drift without requiring you to inspect each host individually.
The storage tier shown under Details connects the pool to storage policies. Policies target tiers, so a disk governed by a given policy is only placed on pools of a matching tier.

Virtual Machines

Lists every virtual machine with one or more disks on this pool — the immediate answer to “what is affected if this pool degrades?” Each row shows the VM’s host, power state, guest status, CPU and memory allocation, allocated versus consumed space, guest hostname, IP address, and pool presence. Use the Search VMs… box to find a specific workload and the Columns selector to tailor the table.
Allocated Space is what the VM’s disks are provisioned to grow to; Consumed Space is what they occupy today. The gap between the two across all VMs on a pool is your thin-provisioning exposure — a pool can be overcommitted on allocation long before Usage % looks alarming.

Browse

A file-level view of the pool’s contents. Navigate folders, search files, and see each item’s size, modification time, and — for disk images — the VM that uses it, which ties files on disk back to the workloads that own them. Toolbar controls:
  • Refresh — reload the current folder listing.
  • New Folder — create a folder in the current location.
  • Upload — upload a file, for example an ISO image or a disk image being imported.
Pools contain system folders used by the platform itself, such as .ha, .ha-heartbeat, and .ha-leader, and may contain folders created by the storage array, such as .snapshot. The .ha* folders back the cluster’s High Availability heartbeat and coordination. Do not modify or delete them — treat anything you did not create through a VM or upload as platform-managed.