Talos Kubernetes Clusters
Talos clusters run Kubernetes on Talos Linux, an immutable, minimal operating system purpose-built for Kubernetes. Talos eliminates SSH access and traditional package managers, reducing your attack surface and simplifying operations.
Talos Linux is fully API-managed, immutable, and contains only the components required to run Kubernetes. This makes clusters more secure, consistent, and easier to upgrade.
Creating a Talos Cluster
Navigate to Kubernetes > Kubernetes and click Create Cluster.
| Field | Description |
|---|---|
| Cluster Name | A unique name for your cluster. Use lowercase letters, numbers, and hyphens. |
| Select Tenant | The tenant that owns the cluster. |
| Select Cloud | The cloud location for the cluster infrastructure. |
| Talos Version | Select the Talos Linux version to use for the cluster nodes. |
| Kubernetes Version | Select the Kubernetes version. Must be compatible with the chosen Talos version. |
| Schematic ID | Optional. A unique identifier for a specific Talos OS image with built-in components from the Talos Factory. |
Control Plane Configuration
Configure the control plane nodes that manage the cluster state and API server:
| Parameter | Description | Recommendation |
|---|---|---|
| CPU Cores | Virtual CPU cores per control plane node. | 2+ cores |
| RAM | Memory per control plane node in GB. | 4+ GB |
| Disk Size | Storage per control plane node in GB. | 50+ GB |
| Node Count | Number of control plane nodes. Use odd numbers for quorum. | 3 for HA |
Worker Node Configuration
Worker nodes run your application workloads. Configure resources based on your expected workload requirements:
| Parameter | Description | Minimum |
|---|---|---|
| CPU Cores | Virtual CPU cores per worker node. | 2 cores |
| RAM | Memory per worker node in GB. | 2 GB |
| Disk Size | Storage per worker node in GB. | 20 GB |
| Node Count | Number of worker nodes. | 1 node |
Click Create to start provisioning. Talos clusters typically take a few minutes to become ready.
Cluster Info and Status
The cluster details page provides an overview of your Talos cluster including:
- Cluster health status and readiness
- Talos Linux version and Kubernetes version
- Control plane and worker node counts
- API server endpoint
- Individual node status and resource utilization
Editing Control Planes
You can modify the control plane configuration after cluster creation. From the cluster details page, navigate to the Control Plane section and click Edit. You can adjust:
- CPU cores and RAM per control plane node
- Disk size per node
- Number of control plane nodes (maintain odd numbers for quorum)
Modifying control plane resources triggers a rolling update. Nodes are updated one at a time to maintain cluster availability. Ensure you have at least 3 control plane nodes for high availability during updates.
Managing Worker Nodes
Worker nodes can be scaled and reconfigured as your workload demands change:
- Scale up: Increase the worker node count to add capacity.
- Scale down: Decrease the node count to reduce costs. Workloads are automatically rescheduled.
- Resize: Modify CPU, RAM, or disk per worker node.
Cluster Resources
The resources view shows the aggregate compute capacity of your cluster, including total and available CPU, memory, and storage across all nodes. Use this view to determine whether you need to scale your cluster.
Upgrading Talos and Kubernetes Versions
Xelon HQ supports in-place upgrades for both Talos Linux and Kubernetes versions. From the cluster details page, click Upgrade and select the target versions.
Check Compatibility
Verify that your target Kubernetes version is compatible with the selected Talos version. The upgrade dialog shows only compatible combinations.
Initiate Upgrade
Select the new Talos and/or Kubernetes version and confirm the upgrade. Control plane nodes are upgraded first, followed by worker nodes.
Monitor Progress
Track the upgrade progress in the cluster details view. Each node shows its current version and upgrade status.
Test version upgrades on a non-production cluster first. Ensure your workloads are compatible with the new Kubernetes version before upgrading production clusters.
Deleting a Cluster
To delete a Talos cluster, navigate to the cluster details page and click Delete Cluster. Confirm the deletion when prompted.
Deleting a cluster permanently destroys all nodes, workloads, persistent volumes, and associated resources. This action is irreversible.