You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/getting-started/requirements.md
+20-17Lines changed: 20 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,25 +21,28 @@ You will need the following tools installed on your workstation:
21
21
22
22
To run this tutorial, you will need the following setup:
23
23
24
-
**Cluster nodes:** three bare-metal servers or virtual machines in the following minimal configuration:
25
-
26
-
- CPU: 4 cores, `x86` architecture.
27
-
- RAM: 16 GiB.
28
-
- Storage: local SSDs recommended:
29
-
- SSD1: 32GiB<br>Primary disk, used for Talos Linux, etcd storage, and downloaded images. Low latency is required.
30
-
- SSD2: 100GiB<br>Secondary disk, used for user application data.
31
-
- OS:
32
-
- Any Linux distribution, for example, Ubuntu.<br>
33
-
- There are [other installation methods]({{% ref "/docs/install/talos" %}}) which require either any Linux or no OS at all to start.
34
-
- Networking:
35
-
- Routable FQDN domain.<br>If you don't have one, you can use [nip.io](https://nip.io/) with dash notation
36
-
- Located in the same L2 network segment.
24
+
**Cluster nodes:** three bare-metal servers or virtual machines. Hardware requirements depend on your usage scenario:
25
+
26
+
{{< include "docs/install/_include/hardware-config-tabs.md">}}
27
+
28
+
**Storage:**
29
+
- **Primary Disk**: Used for Talos Linux, etcd storage, and downloaded images. Low latency is required.
30
+
- **Secondary Disk**: Used for user application data (ZFS pool).
31
+
32
+
**OS:**
33
+
- Any Linux distribution, for example, Ubuntu.<br>
34
+
- There are [other installation methods]({{% ref "/docs/install/talos" %}}) which require either any Linux or no OS at all to start.
35
+
36
+
**Networking:**
37
+
- Routable FQDN domain.<br>If you don't have one, you can use [nip.io](https://nip.io/) with dash notation
38
+
- Located in the same L2 network segment.
37
39
- Anti-spoofing disabled.<br>
38
40
It is required for MetalLB, the load balancer used in Cozystack.
39
-
- If using virtual machines, there are extra requirements:
40
-
- CPU passthrough enabled and CPU model set to `host` in the hypervisor settings.
41
-
- Nested virtualization enabled.<br>
42
-
Required for virtual machines and tenant kubernetes clusters.
41
+
42
+
**Virtual machines:**
43
+
- CPU passthrough enabled and CPU model set to `host` in the hypervisor settings.
44
+
- Nested virtualization enabled.<br>
45
+
Required for virtual machines and tenant kubernetes clusters.
43
46
44
47
For a more detailed explanation of hardware requirements for different setups, refer to the [Hardware Requirements]({{% ref "/docs/install/hardware-requirements" %}})
Copy file name to clipboardExpand all lines: content/en/docs/install/hardware-requirements.md
+9-18Lines changed: 9 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,23 +16,11 @@ in a fully containerized or virtualized environment.
16
16
Hardware requirements depend on your usage scenario.
17
17
Below are several common deployment options; review them to determine which setup fits your needs best.
18
18
19
-
## Small lab
20
-
21
-
Here are the baseline requirements for running a tiny installation.
22
-
The minimum recommended configuration for each node is as follows:
23
-
24
-
| Component | Requirement |
25
-
|------------------|--------------|
26
-
| CPU | 4 cores |
27
-
| CPU Type | host |
28
-
| RAM | 16 GB |
29
-
| Primary Disk | 32 GB SSD |
30
-
| Secondary Disk | 100 GB (raw) |
31
-
19
+
{{< include "docs/install/_include/hardware-config-tabs.md" >}}
32
20
33
21
**Compute:**
34
22
35
-
- Three physical or virtual servers with amd64/x86_64 architecture, with at least 16 GB RAM and 4 CPU cores each.
23
+
- Three or more physical or virtual servers with amd64/x86_64 architecture, with the specifications shown in the table above.
36
24
- Virtualized servers need nested virtualization enabled and the CPU model set to `host` (without emulation).
37
25
- PXE installation requires an extra management instance connected to the same network, with any Linux system able to run a Docker container.
38
26
It should also have `x86-64-v2` architecture, which most probably may be achieved by setting CPU model to `host` in case of a VM.
@@ -50,13 +38,12 @@ Separating disks by role is the primary and more reliable option.
50
38
-**Primary Disk**: This disk contains the Talos Linux operating system, essential system kernel modules and
51
39
Cozystack system base pods, logs, and base container images. Also an etcd cluster will be running on top of it, so a low-latency volume should be used, preferably a local SSD.
52
40
53
-
Minimum: 32 GB; approximately 26 GB is used in a standard Cozystack setup.
54
-
Talos installation expects `/dev/sda` as the system disk (virtio drives usually appear as `/dev/vda`).
41
+
Minimum sizes vary by configuration (see table above). Talos installation expects `/dev/sda` as the system disk (virtio drives usually appear as `/dev/vda`).
55
42
56
43
-**Secondary Disk**: Dedicated to workload data and can be increased based on workload requirements.
57
44
Used for provisioning volumes via PersistentVolumeClaims (PVCs).
58
45
59
-
Suggested: 100 GB. Disk path (usually `/dev/sdb`) will be defined in the storage configuration.
46
+
Minimum sizes vary by configuration (see table above). Disk path (usually `/dev/sdb`) will be defined in the storage configuration.
60
47
It does not affect the Talos installation.
61
48
62
49
Learn more about configuring Linstor StorageClass from the
@@ -73,7 +60,11 @@ Using a local SSD disk is recommended.
73
60
- Machines must be allowed to use additional IPs, or an external load balancer must be available.
74
61
Using additional IPs is disabled by default and must be enabled explicitly in most public clouds.
75
62
- Additional public IPs for ingress and virtual machines may be needed. Check if your public cloud provider supports floating IPs.
76
-
63
+
- Routable FQDN domain (or use [nip.io](https://nip.io/) with dash notation)
64
+
- Located in the same L2 network segment
65
+
- Anti-spoofing disabled (required for MetalLB)
66
+
- Minimum 1 Gbps (10 Gbps recommended for production)
0 commit comments