/device/model`.
# # Disk bus path.
# busPath: /pci0000:00/0000:00:17.0/ata1/host0/target0:0:0/0:0:0:0
@@ -941,37 +926,37 @@ machine:
| `name` |
string |
- Disk name `/sys/block/{"<"}dev{">"}/device/name`. |
+ Disk name `/sys/block//device/name`. |
|
| `model` |
string |
- Disk model `/sys/block/{"<"}dev{">"}/device/model`. |
+ Disk model `/sys/block//device/model`. |
|
| `serial` |
string |
- Disk serial number `/sys/block/{"<"}dev{">"}/serial`. |
+ Disk serial number `/sys/block//serial`. |
|
| `modalias` |
string |
- Disk modalias `/sys/block/{"<"}dev{">"}/device/modalias`. |
+ Disk modalias `/sys/block//device/modalias`. |
|
| `uuid` |
string |
- Disk UUID `/sys/block/{"<"}dev{">"}/uuid`. |
+ Disk UUID `/sys/block//uuid`. |
|
| `wwid` |
string |
- Disk WWID `/sys/block/{"<"}dev{">"}/wwid`. |
+ Disk WWID `/sys/block//wwid`. |
|
@@ -2024,7 +2009,7 @@ APIServerConfig represents the kube apiserver configuration options.
```yaml
cluster:
apiServer:
- image: registry.k8s.io/kube-apiserver:v1.35.0-alpha.3 # The container image used in the API server manifest.
+ image: registry.k8s.io/kube-apiserver:v1.35.0 # The container image used in the API server manifest.
# Extra arguments to supply to the API server.
extraArgs:
feature-gates: ServerSideApply=true
@@ -2377,7 +2362,7 @@ ControllerManagerConfig represents the kube controller manager configuration opt
```yaml
cluster:
controllerManager:
- image: registry.k8s.io/kube-controller-manager:v1.35.0-alpha.3 # The container image used in the controller manager manifest.
+ image: registry.k8s.io/kube-controller-manager:v1.35.0 # The container image used in the controller manager manifest.
# Extra arguments to supply to the controller manager.
extraArgs:
feature-gates: ServerSideApply=true
@@ -2518,7 +2503,7 @@ ProxyConfig represents the kube proxy configuration options.
```yaml
cluster:
proxy:
- image: registry.k8s.io/kube-proxy:v1.35.0-alpha.3 # The container image used in the kube-proxy manifest.
+ image: registry.k8s.io/kube-proxy:v1.35.0 # The container image used in the kube-proxy manifest.
mode: ipvs # proxy mode of kube-proxy.
# Extra arguments to supply to kube-proxy.
extraArgs:
@@ -2579,7 +2564,7 @@ SchedulerConfig represents the kube scheduler configuration options.
```yaml
cluster:
scheduler:
- image: registry.k8s.io/kube-scheduler:v1.35.0-alpha.3 # The container image used in the scheduler manifest.
+ image: registry.k8s.io/kube-scheduler:v1.35.0 # The container image used in the scheduler manifest.
# Extra arguments to supply to the scheduler.
extraArgs:
feature-gates: AllBeta=true
@@ -2877,7 +2862,7 @@ EtcdConfig represents the etcd configuration options.
```yaml
cluster:
etcd:
- image: registry.k8s.io/etcd:v3.6.6 # The container image used to create the etcd service.
+ image: registry.k8s.io/etcd:v3.6.7 # The container image used to create the etcd service.
# The `ca` is the root certificate authority of the PKI.
ca:
crt: LS0tIEVYQU1QTEUgQ0VSVElGSUNBVEUgLS0t
@@ -2948,7 +2933,7 @@ CoreDNS represents the CoreDNS config values.
```yaml
cluster:
coreDNS:
- image: registry.k8s.io/coredns/coredns:v1.13.1 # The `image` field is an override to the default coredns image.
+ image: registry.k8s.io/coredns/coredns:v1.13.2 # The `image` field is an override to the default coredns image.
```
diff --git a/public/talos/v1.13/security/ca-rotation.mdx b/public/talos/v1.13/security/ca-rotation.mdx
index b09d339a..d6c1b779 100644
--- a/public/talos/v1.13/security/ca-rotation.mdx
+++ b/public/talos/v1.13/security/ca-rotation.mdx
@@ -29,7 +29,7 @@ Both rotation flows are described in detail below.
## Talos API
-### Automated Talos API CA Rotation
+### Automated Talos API CA rotation
Talos API CA rotation doesn't interrupt connections within the cluster, and it doesn't require a reboot of the nodes.
@@ -108,7 +108,7 @@ If other client access `talosconfig` files needs to be generated, use `talosctl
> Note: if using [Talos API access from Kubernetes](../../../kubernetes-guides/advanced-guides/talos-api-access-from-k8s) feature, pods might need to be restarted manually to pick up new `talosconfig`.
-### Manual Steps for Talos API CA Rotation
+### Manual steps for Talos API CA rotation
1. Generate new Talos CA (e.g. use `talosctl gen secrets` and use Talos CA).
2. Patch machine configuration on all nodes updating `.machine.acceptedCAs` with new CA certificate.
@@ -120,7 +120,7 @@ If other client access `talosconfig` files needs to be generated, use `talosctl
## Kubernetes API
-### Automated Kubernetes API CA Rotation
+### Automated Kubernetes API CA rotation
The automated process only rotates Kubernetes API CA, used by the `kube-apiserver`, `kubelet`, etc.
Other Kubernetes secrets might need to be rotated manually as required.
@@ -182,7 +182,7 @@ New `kubeconfig` can be fetched with `talosctl kubeconfig` command from the clus
Kubernetes pods might need to be restarted manually to pick up changes to the Kubernetes API CA.
-### Manual Steps for Kubernetes API CA Rotation
+### Manual steps for Kubernetes API CA rotation
Steps are similar [to the Talos API CA rotation](#manual-steps-for-talos-api-ca-rotation), but use:
diff --git a/public/talos/v1.13/security/cert-management.mdx b/public/talos/v1.13/security/cert-management.mdx
index a08c257b..24646df0 100644
--- a/public/talos/v1.13/security/cert-management.mdx
+++ b/public/talos/v1.13/security/cert-management.mdx
@@ -16,9 +16,9 @@ Each time you download the `kubeconfig` file from a Talos Linux cluster, the cli
The `talosconfig` file should be renewed at least once a year, using the `talosctl config new` command, as shown below, or by one of the other methods.
-## Generating New Client Configuration
+## Generating new client configuration
-### Using Controlplane Node
+### Using control plane node
If you have a valid (not expired) `talosconfig` with `os:admin` role,
a new client configuration file can be generated with `talosctl config new` against
@@ -30,7 +30,7 @@ talosctl -n CP1 config new talosconfig-reader --roles os:reader --crt-ttl 24h
A specific [role](./rbac) and certificate lifetime can be specified.
-### From Secrets Bundle
+### From secrets bundle
If a secrets bundle (`secrets.yaml` from `talosctl gen secrets`) was saved while
[generating machine configuration](../getting-started/#configure-talos):
@@ -41,7 +41,7 @@ talosctl gen config --with-secrets secrets.yaml --output-types talosconfig -o ta
> Note: `` and `` arguments don't matter, as they are not used for `talosconfig`.
-### From Control Plane Machine Configuration
+### From control plane machine configuration
In order to create a new key pair for client configuration, you will need the root Talos API CA.
The base64 encoded CA can be found in the control plane node's configuration file.
diff --git a/public/talos/v1.13/security/iam-roles-for-service-accounts.mdx b/public/talos/v1.13/security/iam-roles-for-service-accounts.mdx
index 7d5532e2..3dfc89fd 100644
--- a/public/talos/v1.13/security/iam-roles-for-service-accounts.mdx
+++ b/public/talos/v1.13/security/iam-roles-for-service-accounts.mdx
@@ -204,7 +204,7 @@ Patch your Talos `machineconfig` to use the new Service Account issuer and signi
talosctl apply-config --nodes --file machineconfig-patch.yaml
```
-## Step 3: Install Required Kubernetes Components
+## Step 3: Install required Kubernetes components
Two components are required on the cluster: `cert-manager` and `amazon-eks-pod-identity-webhook`.
diff --git a/public/talos/v1.13/security/verifying-images.mdx b/public/talos/v1.13/security/verifying-images.mdx
index 96a5603f..69dc0d22 100644
--- a/public/talos/v1.13/security/verifying-images.mdx
+++ b/public/talos/v1.13/security/verifying-images.mdx
@@ -11,7 +11,7 @@ Sidero Labs signs the container images generated for the Talos release with [cos
* `ghcr.io/siderolabs/imager` (Talos install image generator)
* all [system extension images](https://github.com/siderolabs/extensions/)
-## Verifying Container Image Signatures
+## Verifying container image signatures
The `cosign` tool can be used to verify the signatures of the Talos container images:
@@ -29,7 +29,7 @@ The following checks were performed on each of these signatures:
The image should be signed using [cosign certificate authority flow](https://docs.sigstore.dev/certificate_authority/certificate-issuing-overview/) by a Sidero Labs employee with and email from `siderolabs.com` domain.
-## Reproducible Builds
+## Reproducible builds
Talos builds for `kernel`, `initramfs`, `talosctl`, ISO image, and container images are reproducible.
So you can verify that the build is the same as the one as provided on [GitHub releases page](https://github.com/siderolabs/talos/releases).
-
-
This guide demonstrates how to set initial machine labels when generating boot media / URL using the `omnictl` CLI tool or using [Image Factory](https://factory.talos.dev) directly.
Both methods allow you to label your machines programmatically.
@@ -65,7 +63,7 @@ These initial labels work not only for ISOs but for most installation media and
This command will print the PXE boot URL and exit.
-## Using Image Factory Directly
+## Using Image Factory directly
Instead of using your Omni instance to generate labeled boot media or PXE URLs, you can use the image factory directly.
@@ -124,7 +122,7 @@ Although Image Factory has a [web UI](https://factory.talos.dev), it is currentl
The version of the Image Factory UI built into Omni **does** support specifying initial machine labels.
-### Omni
+### Omni
Provide the following flags to the Omni container on launch.
diff --git a/public/omni/security-and-authentication/using-saml-with-omni/overview.mdx b/public/omni/security-and-authentication/using-saml-with-omni/overview.mdx
index aabdefca..0cb161fe 100644
--- a/public/omni/security-and-authentication/using-saml-with-omni/overview.mdx
+++ b/public/omni/security-and-authentication/using-saml-with-omni/overview.mdx
@@ -3,4 +3,4 @@ title: Overview
---
Omni can integrate with your enterprise SAML provider for authentication and identity management. See also information about [how SAML impacts Omni authentication.](../../security-and-authentication/authentication-and-authorization) Please contact support@siderolabs.com or your account manager to enable SAML on the SaaS version of Omni (N.B. this is only available for Startup tier and above).
-If using Omni for non-production workloads, you can [self-host](../../infrastructure-and-extensions/self-hosted/overview) and configure SAML yourself.
+If using Omni for non-production workloads, you can [self-host](../../self-hosted/overview) and configure SAML yourself.
diff --git a/public/omni/infrastructure-and-extensions/self-hosted/deploy-image-factory-on-prem.mdx b/public/omni/self-hosted/deploy-image-factory-on-prem.mdx
similarity index 95%
rename from public/omni/infrastructure-and-extensions/self-hosted/deploy-image-factory-on-prem.mdx
rename to public/omni/self-hosted/deploy-image-factory-on-prem.mdx
index 465a0a62..71063db7 100644
--- a/public/omni/infrastructure-and-extensions/self-hosted/deploy-image-factory-on-prem.mdx
+++ b/public/omni/self-hosted/deploy-image-factory-on-prem.mdx
@@ -2,11 +2,11 @@
title: Deploy Image Factory On-prem
---
-import { release } from '/snippets/custom-variables.mdx';
+import { release, version } from '/snippets/custom-variables.mdx';
The [Image Factory](https://github.com/siderolabs/image-factory) is a way for you to dynamically create Talos Linux images. There is a public, hosted version of the Image Factory at [factory.talos.dev](https://factory.talos.dev) and it can also be run in your environment.
-The Image Factory is a critical component of [Omni](../../overview/what-is-omni) to generate installation media and update Talos nodes, but it is not required to use Omni to use the Image Factory. It is a web interface and API for the `imager` command which is used to customize Talos from the command line.
+The Image Factory is a critical component of Omni to generate installation media and update Talos nodes, but it is not required to use Omni to use the Image Factory. It is a web interface and API for the `imager` command which is used to customize Talos from the command line.
## Prerequisites
@@ -30,7 +30,7 @@ If you don't have a container registry available to push images to you can tempo
-## Generate Machine Configurations
+## Generate machine configurations
With the IP address above, you can now generate the machine configurations to use for installing Talos and Kubernetes.
Issue the following command, updating the output directory, cluster name, and control plane IP as you see fit:
@@ -113,7 +113,7 @@ talosctl gen config talos-vbox-cluster https://$CONTROL_PLANE_IP:6443 --output-d
This will create several files in the `_out` directory: controlplane.yaml, worker.yaml, and talosconfig.
-## Create Control Plane Node
+## Create control plane node
Using the `controlplane.yaml` generated above, you can now apply this config using talosctl.
Issue:
@@ -133,7 +133,7 @@ Talos will be installed to disk, the VM will reboot, and then Talos will configu
>
> Simply remove the ISO image from the VM and restart it.
-## Create Worker Node
+## Create worker node
Create at least a single worker node using a process similar to the control plane creation above.
Start the worker node VM and wait for it to enter "maintenance mode".
@@ -167,7 +167,7 @@ You should see stage change to `Running` and your cluster is now ready.
talosctl --talosconfig $TALOSCONFIG bootstrap
```
-## Using the Cluster
+## Using the cluster
Once the cluster is available, you can make use of `talosctl` and `kubectl` to interact with the cluster.
For example, to view current running containers, run `talosctl containers` for a list of containers in the `system` namespace, or `talosctl containers -k` for the `k8s.io` namespace.
@@ -197,6 +197,6 @@ You can then use kubectl in this fashion:
kubectl get nodes
```
-## Cleaning Up
+## Cleaning up
To cleanup, simply stop and delete the virtual machines from the VirtualBox UI.
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/bananapi_m64.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/bananapi_m64.mdx
index b160a0c5..2d63efb2 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/bananapi_m64.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/bananapi_m64.mdx
@@ -23,7 +23,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image using Image Factory
+## Download the image using Image Factory
The default schematic id for "vanilla" Banana Pi M64 is `8e11dcb3c2803fbe893ab201fcadf1ef295568410e7ced95c6c8b122a5070ce4`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -37,7 +37,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
The path to your SD card can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
@@ -48,7 +48,7 @@ Now `dd` the image to your SD card:
sudo dd if=metal-arm64.raw of=/dev/mmcblk0 conv=fsync bs=4M
```
-## Bootstrapping the Node
+## Bootstrapping the node
Insert the SD card to your board, turn it on and wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/jetson_nano.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/jetson_nano.mdx
index 8b00a229..5a18b7c9 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/jetson_nano.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/jetson_nano.mdx
@@ -85,7 +85,7 @@ This will flash the firmware to the Jetson Nano SPI flash and you'll see a lot o
If you've connected the serial console you'll also see the progress there.
Once the flashing is done you can disconnect the USB cable and power off the Jetson Nano.
-## Download the Image
+## Download the image
The default schematic id for "vanilla" Jetson Nano is `c7d6f36c6bdfb45fd63178b202a67cff0dd270262269c64886b43f76880ecf1e`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -99,7 +99,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
Now `dd` the image to your SD card/USB storage:
@@ -109,7 +109,7 @@ sudo dd if=metal-arm64.raw of=/dev/mmcblk0 conv=fsync bs=4M status=progress
| Replace `/dev/mmcblk0` with the name of your SD card/USB storage.
-## Bootstrapping the Node
+## Bootstrapping the node
Insert the SD card/USB storage to your board, turn it on and wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/libretech_all_h3_cc_h5.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/libretech_all_h3_cc_h5.mdx
index 8e644817..05b53931 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/libretech_all_h3_cc_h5.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/libretech_all_h3_cc_h5.mdx
@@ -23,7 +23,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image
+## Download the image
The default schematic id for "vanilla" Libretech H3 CC H5 is `5689d7795f91ac5bf6ccc85093fad8f8b27f6ea9d96a9ac5a059997bffd8ad5c`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -37,7 +37,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
The path to your SD card can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
@@ -48,7 +48,7 @@ Now `dd` the image to your SD card:
sudo dd if=metal-arm64.raw of=/dev/mmcblk0 conv=fsync bs=4M
```
-## Bootstrapping the Node
+## Bootstrapping the node
Insert the SD card to your board, turn it on and wait for the console to show you the instructions for bootstrapping the node.
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/nanopi_r4s.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/nanopi_r4s.mdx
index 29b63c55..e814098f 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/nanopi_r4s.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/nanopi_r4s.mdx
@@ -23,7 +23,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image
+## Download the image
The default schematic id for "vanilla" NanoPi R4S is `5f74a09891d5830f0b36158d3d9ea3b1c9cc019848ace08ff63ba255e38c8da4`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -37,7 +37,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
The path to your SD card can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
@@ -48,7 +48,7 @@ Now `dd` the image to your SD card:
sudo dd if=metal-arm64.raw of=/dev/mmcblk0 conv=fsync bs=4M
```
-## Bootstrapping the Node
+## Bootstrapping the node
Insert the SD card to your board, turn it on and wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_5.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_5.mdx
index 1f9a00e7..791d0697 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_5.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_5.mdx
@@ -34,7 +34,7 @@ xz -d metal-arm64.raw.xz
`}
-#### Flash the Image
+#### Flash the image
The image can be flashed using Etcher on Windows, macOS, or Linux or using dd on Linux:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_r1_plus_lts.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_r1_plus_lts.mdx
index 4dac721a..2570fcfa 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_r1_plus_lts.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/orangepi_r1_plus_lts.mdx
@@ -21,7 +21,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image using Image Factory
+## Download the image using Image Factory
The default schematic id for "vanilla" Orange Pi R1 Plus LTS is `da388062cd9318efdc7391982a77ebb2a97ed4fbda68f221354c17839a750509`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -35,7 +35,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
The path to your SD card can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/pine64.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/pine64.mdx
index 4916cd52..dd6edb83 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/pine64.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/pine64.mdx
@@ -23,7 +23,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image
+## Download the image
The default schematic id for "vanilla" Pine64 is `185431e0f0bf34c983c6f47f4c6d3703aa2f02cd202ca013216fd71ffc34e175`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -37,7 +37,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
The path to your SD card can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
@@ -48,7 +48,7 @@ Now `dd` the image to your SD card:
sudo dd if=metal-arm64.raw of=/dev/mmcblk0 conv=fsync bs=4M
```
-## Bootstrapping the Node
+## Bootstrapping the node
Insert the SD card to your board, turn it on and wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/rock4cplus.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/rock4cplus.mdx
index 6edf0367..f1ee19ae 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/rock4cplus.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/rock4cplus.mdx
@@ -21,7 +21,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image
+## Download the image
The default schematic id for "vanilla" Rock 4c Plus is `ed7091ab924ef1406dadc4623c90f245868f03d262764ddc2c22c8a19eb37c1c`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -54,7 +54,7 @@ The user has two options to proceed:
Insert the SD card into the board, turn it on and proceed to [bootstrapping the node](#bootstrapping-the-node).
-## Bootstrapping the Node
+## Bootstrapping the node
Wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/rock5b.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/rock5b.mdx
index 3aafbcb8..5cd93da1 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/rock5b.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/rock5b.mdx
@@ -14,7 +14,7 @@ You will need
- follow [Installation/talosctl](../../getting-started/talosctl ) to intall `talosctl`
- an SD card
-## Download the Image
+## Download the image
Visit the [Image Factory](https://factory.talos.dev/), select `Single Board Computers`, select the version and select `Radxa ROCK 5B` from the options.
@@ -30,7 +30,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
This guide assumes the node should boot from SD card.
Booting from eMMC or NVMe has not been tested yet.
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/rock64.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/rock64.mdx
index e5ff809a..c9ec9eb9 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/rock64.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/rock64.mdx
@@ -23,7 +23,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image
+## Download the image
The default schematic id for "vanilla" Pine64 Rock64 is `0e162298269125049a51ec0a03c2ef85405a55e1d2ac36a7ef7292358cf3ce5a`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -37,7 +37,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
The path to your SD card can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
@@ -48,7 +48,7 @@ Now `dd` the image to your SD card:
sudo dd if=metal-arm64.raw of=/dev/mmcblk0 conv=fsync bs=4M
```
-## Bootstrapping the Node
+## Bootstrapping the node
Insert the SD card to your board, turn it on and wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4.mdx
index 3b9fa2f8..c32b2e1f 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4.mdx
@@ -24,7 +24,7 @@ chmod +x /usr/local/bin/talosctl
-## Download the Image
+## Download the image
The default schematic id for "vanilla" RockPi 4 is `25d2690bb48685de5939edd6dee83a0e09591311e64ad03c550de00f8a521f51`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -39,7 +39,7 @@ xz -d metal-arm64.raw.xz
-## Writing the Image
+## Writing the image
The path to your SD card/eMMC/USB/nVME can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
@@ -68,7 +68,7 @@ Follow the Radxa docs on [Install on M.2 NVME SSD](https://wiki.radxa.com/Rockpi
After these above steps, Talos will boot from the nVME/USB and enter maintenance mode.
Proceed to [bootstrapping the node](#bootstrapping-the-node).
-## Bootstrapping the Node
+## Bootstrapping the node
Wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4c.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4c.mdx
index 7e512b46..a88840d3 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4c.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/rockpi_4c.mdx
@@ -21,7 +21,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image
+## Download the image
The default schematic id for "vanilla" RockPi 4c is `08e72e242b71f42c9db5bed80e8255b2e0d442a372bc09055b79537d9e3ce191`.
Refer to the [Image Factory](../../learn-more/image-factory) documentation for more information.
@@ -35,7 +35,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
The path to your SD card/eMMC/USB/nVME can be found using `fdisk` on Linux or `diskutil` on macOS.
In this example, we will assume `/dev/mmcblk0`.
@@ -64,7 +64,7 @@ Follow the Radxa docs on [Install on M.2 NVME SSD](https://wiki.radxa.com/Rockpi
After these above steps, Talos will boot from the nVME/USB and enter maintenance mode.
Proceed to [bootstrapping the node](#bootstrapping-the-node).
-## Bootstrapping the Node
+## Bootstrapping the node
Wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/rpi_generic.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/rpi_generic.mdx
index c90571a5..9caddcdb 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/rpi_generic.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/rpi_generic.mdx
@@ -11,7 +11,7 @@ Talos disk image for the Raspberry Pi generic should in theory work for the boar
This has only been officialy tested on the Raspberry Pi 4 and community tested on one variant of the Compute Module 4 using Super 6C boards.
If you have tested this on other Raspberry Pi boards, please let us know.
-## Video Walkthrough
+## Video walkthrough
To see a live demo of this writeup, see the video below:
@@ -44,7 +44,7 @@ Power off the Raspberry Pi and remove the SD card from it.
> Note: Updating the bootloader only needs to be done once.
-## Download the Image
+## Download the image
> Note: if you need to enable Broadcom VideoCore GPU support, generate a new image from the [Image Factory](../../learn-more/image-factory) with the correct [config.txt](#configtxt-information) configuration and `vc4` system extension.
> More information can be found under the [Image Factory Example](#example-raspberry-pi-generic-with-broadcom-videocore-gpu-support-with-image-factory) below.
@@ -60,7 +60,7 @@ xz -d metal-arm64.raw.xz
`}
-## Writing the Image
+## Writing the image
Now `dd` the image to your SD card:
@@ -68,7 +68,7 @@ Now `dd` the image to your SD card:
sudo dd if=metal-arm64.raw of=/dev/mmcblk0 conv=fsync bs=4M
```
-## Bootstrapping the Node
+## Bootstrapping the node
Insert the SD card to your board, turn it on and wait for the console to show you the instructions for bootstrapping the node.
Following the instructions in the console output to connect to the interactive installer:
@@ -300,7 +300,7 @@ Now we can use the customized `installer` image to install Talos on Raspberry Pi
When it's time to upgrade a machine, a new `installer` image can be generated using the new version of `imager`, and updating the system extension and overlay images to the matching versions.
The custom `installer` image can now be used to upgrade Talos machine.
-## config.txt Information
+## config.txt information
Refer to the default [config.txt](https://github.com/siderolabs/sbc-raspberrypi/blob/main/installers/rpi_generic/src/config.txt) file used by the [sbc-raspberrypi](https://github.com/siderolabs/sbc-raspberrypi) overlay.
@@ -363,7 +363,7 @@ The following table can be used to troubleshoot booting issues:
| 4 | 6 | Power failure type A |
| 4 | 7 | Power failure type B |
-### GPU Memory Issues
+### GPU memory issues
The Contiguous Memory Allocator (CMA) reserves physically contiguous memory for Raspberry Pi GPU/display operations (e.g., KMS/DRM rendering).
An error like `DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory` indicates an undersized CMA pool for graphics tasks.
@@ -381,7 +381,7 @@ The default may be too small for GPU-intensive tasks, and oversizing reduces sys
| 512 MB | 4K media, ML with GPU |
| 1024 MB | Experimental, may destabilize |
-#### Change CMA Size
+#### Change CMA size
**Kernel Parameters**:
diff --git a/public/talos/v1.12/platform-specific-installations/single-board-computers/turing_rk1.mdx b/public/talos/v1.12/platform-specific-installations/single-board-computers/turing_rk1.mdx
index 3a55b7e0..bad04d36 100644
--- a/public/talos/v1.12/platform-specific-installations/single-board-computers/turing_rk1.mdx
+++ b/public/talos/v1.12/platform-specific-installations/single-board-computers/turing_rk1.mdx
@@ -24,7 +24,7 @@ chmod +x /usr/local/bin/talosctl
`}
-## Download the Image
+## Download the image
Go to `https://factory.talos.dev` select `Single Board Computers`, select the version and select `Turing RK1` from the options.
Choose your desired extensions and fill in the kernel command line arguments if needed.
@@ -105,7 +105,7 @@ Skip step 1 if you already installed your NVMe drive.
Talos will now boot from the NVMe/USB and enter maintenance mode.
-## Bootstrapping the Node
+## Bootstrapping the node
To monitor boot messages, run: (repeat)
diff --git a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/hyper-v.mdx b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/hyper-v.mdx
index 6d8b2f93..64ce8276 100644
--- a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/hyper-v.mdx
+++ b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/hyper-v.mdx
@@ -23,7 +23,7 @@ aliases:
```
- Confirm the change when prompted.
-## Plan Overview
+## Plan overview
We will create a basic 3-node cluster with one control-plane node and two worker nodes.
The main difference between the control plane and worker nodes is the amount of RAM and an additional storage VHD for the worker nodes.
@@ -33,7 +33,7 @@ We use a `VMNamePrefix` argument for the VM name prefix, not the full hostname.
This command will find any existing VM with that prefix and increment the highest suffix found.
For example, if `talos-cp01` and `talos-cp02` exist, it will create VMs starting from `talos-cp03`, depending on the `NumberOfVMs` argument.
-## Setup a Control Plane Node
+## Setup a control plane node
> Note: Ensure the `LAB` adapter exists in Hyper-V and is set to external.
@@ -45,7 +45,7 @@ New-TalosVM -VMNamePrefix talos-cp -CPUCount 2 -StartupMemory 4GB -SwitchName LA
This will create the `talos-cp01` VM and power it on.
-## Setup Worker Nodes
+## Setup worker nodes
Create two worker nodes with the following command:
@@ -55,7 +55,7 @@ New-TalosVM -VMNamePrefix talos-worker -CPUCount 4 -StartupMemory 8GB -SwitchNam
This will create `talos-worker01` and `talos-worker02` VMs, each with an additional 50GB VHD for storage (which can be used for Mayastor).
-## Push Config to the Nodes
+## Push config to the nodes
Once the VMs are ready, find their IP addresses from the VM console.
Push the config to the control plane node with:
@@ -71,7 +71,7 @@ talosctl gen config talos-cluster https://$($CONTROL_PLANE_IP):6443 --output-dir
talosctl apply-config --insecure --nodes $CONTROL_PLANE_IP --file .\controlplane.yaml
```
-## Push Config to Worker Nodes
+## Push config to worker nodes
Similarly, for the worker nodes:
@@ -81,7 +81,7 @@ talosctl apply-config --insecure --nodes 10.10.10.x --file .\worker.yaml
Apply the config to both worker nodes.
-## Bootstrap Cluster
+## Bootstrap cluster
With the nodes ready, bootstrap the Kubernetes cluster:
diff --git a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/kvm.mdx b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/kvm.mdx
index 88b3f6da..97ccf6a1 100644
--- a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/kvm.mdx
+++ b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/kvm.mdx
@@ -30,7 +30,7 @@ cd ~/talos-kvm
Download the latest `metal-amd64.iso` from the Talos [GitHub releases page](https://github.com/siderolabs/talos/releases).
-## Configure the Network
+## Configure the network
Before we get started, let’s set up an isolated network for your Talos cluster.
@@ -116,7 +116,7 @@ Autostart: yes
Bridge: talos-bridge
```
-## Provisioning the Environment
+## Provisioning the environment
Now that you have a dedicated network let's go ahead and provision VMs.
@@ -163,7 +163,7 @@ Use the following command to verify that your VMs are in a running state:
virsh list
```
-## Configure the Cluster
+## Configure the cluster
Now that you have your VMs provisioned it's time to configure the cluster. This step is done through `talosctl` command utility.
@@ -214,7 +214,7 @@ talosctl apply-config --insecure --nodes $NODE_IP --file configs/worker.yaml
At this point your VMs will reboot.
-## Bootstrapping the Cluster
+## Bootstrapping the cluster
After your VMs restart, you can bootstrap the cluster. Bootstrap simply means starting up your Kubernetes cluster for the first time.
diff --git a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/proxmox.mdx b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/proxmox.mdx
index 88554955..c79d080f 100644
--- a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/proxmox.mdx
+++ b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/proxmox.mdx
@@ -9,7 +9,7 @@ import { release_v1_12 } from '/snippets/custom-variables.mdx';
In this guide we will create a Kubernetes cluster using Proxmox.
-## Video Walkthrough
+## Video walkthrough
To see a live demo of this writeup, visit Youtube here:
@@ -17,7 +17,7 @@ To see a live demo of this writeup, visit Youtube here:
## Installation
-### How to Get Proxmox
+### How to get Proxmox
It is assumed that you have already installed Proxmox onto the server you wish to create Talos VMs on.
Visit the [Proxmox](https://www.proxmox.com/en/downloads) downloads page if necessary.
@@ -32,7 +32,7 @@ brew install siderolabs/tap/talosctl
For manual installation and other platforms please see the [talosctl installation guide](../../getting-started/talosctl ).
-### Download ISO Image
+### Download ISO image
In order to install Talos in Proxmox, you will need the ISO image from [Image Factory](https://www.talos.dev/latest/talos-guides/install/boot-assets/#image-factory).
@@ -188,7 +188,7 @@ You can also repeat this for additional nodes desired.
> Doing so will cause Talos to be unable to see all available memory and have insufficient memory to complete
> installation of the cluster.
-## Start Control Plane Node
+## Start control plane node
Once the VMs have been created and updated, start the VM that will be the first control plane node.
This VM will boot the ISO image specified earlier and enter "maintenance mode".
@@ -226,7 +226,7 @@ linux /boot/vmlinuz init_on_alloc=1 slab_nomerge pti=on panic=0 consoleblank=0 p
Then press Ctrl-x or F10
-## Generate Machine Configurations
+## Generate machine configurations
With the IP address above, you can now generate the machine configurations to use for installing Talos and Kubernetes.
Issue the following command, updating the output directory, cluster name, and control plane IP as you see fit:
@@ -264,7 +264,7 @@ talosctl gen config talos-proxmox-cluster https://$CONTROL_PLANE_IP:6443 --outpu
- If you did include the extension, go to your VM → **Options** and set **QEMU Guest Agent** to **Enabled**.
-## Create Control Plane Node
+## Create control plane node
Using the `controlplane.yaml` generated above, you can now apply this config using talosctl.
Issue:
@@ -279,7 +279,7 @@ The VM will remain in stage `Booting` until the bootstrap is completed in a late
> Note: This process can be repeated multiple times to create an HA control plane.
-## Create Worker Node
+## Create worker node
Create at least a single worker node using a process similar to the control plane creation above.
Start the worker node VM and wait for it to enter "maintenance mode".
@@ -293,7 +293,7 @@ talosctl apply-config --insecure --nodes $WORKER_IP --file _out/worker.yaml
> Note: This process can be repeated multiple times to add additional workers.
-## Using the Cluster
+## Using the cluster
Once the cluster is available, you can make use of `talosctl` and `kubectl` to interact with the cluster.
For example, to view current running containers, run `talosctl containers` for a list of containers in the `system` namespace, or `talosctl containers -k` for the `k8s.io` namespace.
@@ -307,7 +307,7 @@ talosctl config endpoint $CONTROL_PLANE_IP
talosctl config node $CONTROL_PLANE_IP
```
-### Bootstrap Etcd
+### Bootstrap etcd
```bash
talosctl bootstrap
@@ -323,7 +323,7 @@ talosctl kubeconfig .
## Troubleshooting
-### Cluster Creation Issues
+### Cluster creation issues
If `talosctl cluster create` fails with disk controller errors:
@@ -337,7 +337,7 @@ If `talosctl cluster create` fails with disk controller errors:
talosctl cluster create --disks scsi:10GiB
```
-### Network Connectivity Issues
+### Network connectivity issues
If nodes fail to obtain IP addresses or show "network is unreachable" errors:
@@ -361,10 +361,10 @@ If nodes fail to obtain IP addresses or show "network is unreachable" errors:
- **Bootstrap hangs**: If bootstrap hangs or disks aren't discovered, verify you're using **VirtIO SCSI** (not "VirtIO SCSI Single")
- **Disk not found**: Check disk path using `talosctl get disks --insecure --nodes $CONTROL_PLANE_IP` and update `install.disk` in machine config if needed (e.g., `install.disk: /dev/vda`)
-### Secure Boot
+### Secure boot
For Secure Boot setup, see the [Secure Boot documentation](../bare-metal-platforms/secureboot).
-## Cleaning Up
+## Cleaning up
To cleanup, simply stop and delete the virtual machines from the Proxmox UI.
diff --git a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/vmware.mdx b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/vmware.mdx
index 71157cbb..07185b3d 100644
--- a/public/talos/v1.12/platform-specific-installations/virtualized-platforms/vmware.mdx
+++ b/public/talos/v1.12/platform-specific-installations/virtualized-platforms/vmware.mdx
@@ -7,12 +7,12 @@ aliases:
import { release_v1_12, release_branch_v1_12 } from '/snippets/custom-variables.mdx';
-## Creating a Cluster via the `govc` CLI
+## Creating a cluster via the `govc` CLI
In this guide we will create an HA Kubernetes cluster with 2 worker nodes.
We will use the `govc` cli which can be downloaded [here](https://github.com/vmware/govmomi/tree/master/govc#installation).
-## Prereqs/Assumptions
+## Prerequisites
This guide will use the virtual IP ("VIP") functionality that is built into Talos in order to provide a stable, known IP for the Kubernetes control plane.
This simply means the user should pick an IP on their "VM Network" to designate for this purpose and keep it handy for future steps.
@@ -24,9 +24,9 @@ To check your version of ESXi refer to the following Broadcom
More information regarding virtual machine hardware versions can be found in the following Broadcom
[KB article](https://knowledge.broadcom.com/external/article/315655/virtual-machine-hardware-versions.html).
-## Create the Machine Configuration Files
+## Create the machine configuration files
-### Generating Base Configurations
+### Generating base configurations
Using the VIP chosen in the prereq steps, we will now generate the base configuration files for the Talos machines.
This can be done with the `talosctl gen config ...` command.
@@ -66,7 +66,7 @@ created talosconfig
At this point, you can modify the generated configs to your liking if needed.
Optionally, you can specify additional patches by adding to the `cp.patch.yaml` file downloaded earlier, or create your own patch files.
-### Validate the Configuration Files
+### Validate the configuration files
```bash
$ talosctl validate --config controlplane.yaml --mode cloud
@@ -90,7 +90,7 @@ cluster:
- --flannel-backend=host-gw
```
-## Set Environment Variables
+## Set environment variables
`govc` makes use of the following environment variables
@@ -111,13 +111,13 @@ export GOVC_DATASTORE=