alt-orchestra/talos
2
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix a typo in QEMU VM setup guide

Browse Source 
Fix a typo in the QEMU VM docs.

Signed-off-by: Andrei Dobre <andreidobre.web@gmail.com>
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
This commit is contained in:
Andrei Dobre 2022-04-04 08:05:36 +03:00 committed by Andrey Smirnov
parent 663e3e8796
commit 5192ba4e23
No known key found for this signature in database
GPG Key ID: 7B26396447AB6DFD
10 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/v0.10/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v0.11/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v0.12/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v0.13/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v0.14/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v0.7/local-platforms/qemu.md
View File

@ -90,7 +90,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v0.8/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v0.9/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v1.0/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster

2
website/content/v1.1/local-platforms/qemu.md
View File

@ -91,7 +91,7 @@ Before the first cluster is created, `talosctl` will download the CNI bundle for
Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be
downloaded and merged into default kubectl config location (`~/.kube/config`).
Cluster provisioning process can be optimized with [registry pull-through cahces](../../guides/configuring-pull-through-cache/).
Cluster provisioning process can be optimized with [registry pull-through caches](../../guides/configuring-pull-through-cache/).
## Using the Cluster