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.
Talos Director is a management platform for the data center. It runs virtual machines, Kubernetes clusters, storage, and networking on Talos Linux and the Talos hypervisor, and you manage all of it through the Talos Director console and API. The immutable, declarative configuration that keeps Talos Kubernetes clusters from drifting applies to virtual machine workloads as well. Talos Director is built for organizations moving off VMware and similar platforms: its migration engine converts existing VMware virtual machines and Kubernetes clusters without application changes.

How the pieces fit together

Talos Director is the management layer. The work itself happens on the hosts.
Virtual machines
Windows and Linux guests
Kubernetes clusters
Talos Linux nodes, managed through Omni
Talos Director: console and API for everything above the hosts
Compute
clusters, hosts, VMs, storage
Kubernetes
create, scale, upgrade
Networking
virtual networks
Security
micro-segmentation
Talos Linux with the KVM hypervisor, on every host: immutable, API-driven, no shell or SSH
Servers, shared storage, and network in your data center
Each server runs Talos Linux with the KVM hypervisor, which executes the virtual machines placed on it. Talos Director sits above the hosts: it groups them into clusters, places and moves virtual machines, attaches storage and networking, and creates Kubernetes clusters on top. Kubernetes nodes created by Talos Director are virtual machines too, running Talos Linux on the same hosts, and Talos Director manages their lifecycle through Omni, Sidero’s Kubernetes management platform. Registering a host with Talos Director brings that machine under management, so Talos Director can see its capacity and place workloads on it. Registering a host does not create any virtual machines or Kubernetes nodes by itself.

What Talos Director does

  • Compute clusters. Hosts are grouped into clusters that share storage. A resource scheduler places virtual machines and rebalances load across hosts using performance metrics, within the overcommit limits you set.
  • Live migration and High Availability. Virtual machines move between hosts without downtime, and when a host fails, its virtual machines restart on the surviving hosts.
  • Rolling host upgrades. Hosts are upgraded one at a time while their workloads keep running.
  • Kubernetes clusters. Talos Director creates and operates Talos Kubernetes clusters on virtual machines through Omni, including node pools, autoscaling, backups, add-ons, and guarded upgrades.
  • Networking. Micro-segmentation and live traffic analysis for virtual machine networks.
  • VMware migration. Converts existing VMware virtual machines and Kubernetes clusters to run on Talos Director.

Documentation in this section

This documentation covers the main areas of the Talos Director console and grows as the product approaches general availability.
  • How Talos Director Works: the parts of a deployment, how a server becomes a host, what happens when a host fails, and how VMs and Kubernetes clusters share the platform.
  • vSphere Concepts in Talos Director: vSphere terms mapped to Talos Director, and where the two differ.
  • Requirements and Supported Platforms: servers, storage, networking, guests, and migration sources, and how far each is validated.
  • API and Automation: the Talos Director API, Terraform plans, and kubectl access to Kubernetes clusters.
  • Clusters: compute cluster health and capacity, scheduling and HA settings, and rolling upgrades.
  • Hosts: adding hosts, and host health, hardware, services, and maintenance.
  • Virtual Machines: creating VMs, and power, console, disks, networking, snapshots, and backups.
  • Migrate from VMware: converting vCenter VMs and choosing a cutover mode.
  • What Happens During a Migration: where a conversion runs, what each stage changes, and what each cutover mode does to the source VM.
  • Storage Pools: shared datastores, host mounts, and the virtual machines that depend on them.
  • Kubernetes Clusters: the Kubernetes fleet dashboard, cluster creation, and day-to-day cluster operations.
  • Virtual Networks: VLAN-backed networks for VMs, and importing networks from Cisco ACI.
  • Security: VM micro-segmentation, and security posture and compliance across Kubernetes clusters.