Skip to content

Commit 451cb5f

Browse files
committed
docs: clarify disk partition confusion
fixed the docs contradiction on disk partitioning Signed-off-by: Amarachi Iheanacho <amarachi.iheanacho@siderolabs.com>
1 parent a2122ee commit 451cb5f

File tree

3 files changed

+12
-18
lines changed

3 files changed

+12
-18
lines changed

website/content/v1.10/introduction/system-requirements.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -62,10 +62,8 @@ These requirements are similar to that of Kubernetes.
6262

6363
## Storage
6464

65-
Talos Linux itself only requires less than 100 MB of disk space, but the EPHEMERAL partition is used to store pulled images, container work directories, and so on.
66-
Thus a minimum is 10 GiB of disk space is required.
67-
100 GiB is desired.
68-
Note, however, that because Talos Linux assumes complete control of the disk it is installed on, so that it can control the partition table for image based upgrades, you cannot partition the rest of the disk for use by workloads.
65+
Talos Linux itself only requires less than 100 MB of disk space, but the EPHEMERAL partition is used to store pulled images, container work directories, and so on. Thus a minimum of 10 GiB of disk space is required. 100 GiB is recommended.
6966

70-
Thus it is recommended to install Talos Linux on a small, dedicated disk - using a Terabyte sized SSD for the Talos install disk would be wasteful.
71-
Sidero Labs recommends having separate disks (apart from the Talos install disk) to be used for storage.
67+
Talos manages disk partitioning automatically during installation, creating EFI, META, STATE, and EPHEMERAL partitions. The EPHEMERAL partition then expands to fill all the space left after the first three. That space can either remain entirely with EPHEMERAL or be divided into additional user volumes, depending on your needs. See [Disk Layout]({{< relref "../talos-guides/configuration/disk-management.md" >}}) for details.
68+
69+
For production, it is often more efficient to dedicate a smaller disk for the Talos installation itself, and use additional disks for workload storage. Using a large, single disk for both system and workloads is supported, but may not be optimal depending on your environment.

website/content/v1.11/introduction/system-requirements.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -62,10 +62,8 @@ These requirements are similar to that of Kubernetes.
6262

6363
## Storage
6464

65-
Talos Linux itself only requires less than 100 MB of disk space, but the EPHEMERAL partition is used to store pulled images, container work directories, and so on.
66-
Thus a minimum is 10 GiB of disk space is required.
67-
100 GiB is desired.
68-
Note, however, that because Talos Linux assumes complete control of the disk it is installed on, so that it can control the partition table for image based upgrades, you cannot partition the rest of the disk for use by workloads.
65+
Talos Linux itself only requires less than 100 MB of disk space, but the EPHEMERAL partition is used to store pulled images, container work directories, and so on. Thus a minimum of 10 GiB of disk space is required. 100 GiB is recommended.
6966

70-
Thus it is recommended to install Talos Linux on a small, dedicated disk - using a Terabyte sized SSD for the Talos install disk would be wasteful.
71-
Sidero Labs recommends having separate disks (apart from the Talos install disk) to be used for storage.
67+
Talos manages disk partitioning automatically during installation, creating EFI, META, STATE, and EPHEMERAL partitions. The EPHEMERAL partition then expands to fill all the space left after the first three. That space can either remain entirely with EPHEMERAL or be divided into additional user volumes, depending on your needs. See [Disk Layout]({{< relref "../talos-guides/configuration/disk-management.md" >}}) for details.
68+
69+
For production, it is often more efficient to dedicate a smaller disk for the Talos installation itself, and use additional disks for workload storage. Using a large, single disk for both system and workloads is supported, but may not be optimal depending on your environment.

website/content/v1.12/introduction/system-requirements.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -62,10 +62,8 @@ These requirements are similar to that of Kubernetes.
6262

6363
## Storage
6464

65-
Talos Linux itself only requires less than 100 MB of disk space, but the EPHEMERAL partition is used to store pulled images, container work directories, and so on.
66-
Thus a minimum is 10 GiB of disk space is required.
67-
100 GiB is desired.
68-
Note, however, that because Talos Linux assumes complete control of the disk it is installed on, so that it can control the partition table for image based upgrades, you cannot partition the rest of the disk for use by workloads.
65+
Talos Linux itself only requires less than 100 MB of disk space, but the EPHEMERAL partition is used to store pulled images, container work directories, and so on. Thus a minimum of 10 GiB of disk space is required. 100 GiB is recommended.
6966

70-
Thus it is recommended to install Talos Linux on a small, dedicated disk - using a Terabyte sized SSD for the Talos install disk would be wasteful.
71-
Sidero Labs recommends having separate disks (apart from the Talos install disk) to be used for storage.
67+
Talos manages disk partitioning automatically during installation, creating EFI, META, STATE, and EPHEMERAL partitions. The EPHEMERAL partition then expands to fill all the space left after the first three. That space can either remain entirely with EPHEMERAL or be divided into additional user volumes, depending on your needs. See [Disk Layout]({{< relref "../talos-guides/configuration/disk-management.md" >}}) for details.
68+
69+
For production, it is often more efficient to dedicate a smaller disk for the Talos installation itself, and use additional disks for workload storage. Using a large, single disk for both system and workloads is supported, but may not be optimal depending on your environment.

0 commit comments

Comments
 (0)