From 71857fd4d3a262a6b41cad3af7d3abb7355d8509 Mon Sep 17 00:00:00 2001 From: Fabian Topfstedt Date: Wed, 26 Jun 2024 11:57:24 +0200 Subject: [PATCH] docs: fix typo: `messure` -> `measure` Fix clilum docs typo.: Signed-off-by: Fabian Topfstedt Signed-off-by: Noel Georgi --- .../content/v1.0/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.1/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.2/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.3/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.4/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.5/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.6/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.7/kubernetes-guides/network/deploying-cilium.md | 2 +- .../content/v1.8/kubernetes-guides/network/deploying-cilium.md | 2 +- 9 files changed, 9 insertions(+), 9 deletions(-) diff --git a/website/content/v1.0/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.0/kubernetes-guides/network/deploying-cilium.md index 1de0347e45..7579ea9966 100644 --- a/website/content/v1.0/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.0/kubernetes-guides/network/deploying-cilium.md @@ -177,7 +177,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ## Known issues diff --git a/website/content/v1.1/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.1/kubernetes-guides/network/deploying-cilium.md index 1de0347e45..7579ea9966 100644 --- a/website/content/v1.1/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.1/kubernetes-guides/network/deploying-cilium.md @@ -177,7 +177,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ## Known issues diff --git a/website/content/v1.2/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.2/kubernetes-guides/network/deploying-cilium.md index 1de0347e45..7579ea9966 100644 --- a/website/content/v1.2/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.2/kubernetes-guides/network/deploying-cilium.md @@ -177,7 +177,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ## Known issues diff --git a/website/content/v1.3/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.3/kubernetes-guides/network/deploying-cilium.md index 1de0347e45..7579ea9966 100644 --- a/website/content/v1.3/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.3/kubernetes-guides/network/deploying-cilium.md @@ -177,7 +177,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ## Known issues diff --git a/website/content/v1.4/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.4/kubernetes-guides/network/deploying-cilium.md index 93d7205bb4..228c85f17e 100644 --- a/website/content/v1.4/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.4/kubernetes-guides/network/deploying-cilium.md @@ -280,7 +280,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ## Known issues diff --git a/website/content/v1.5/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.5/kubernetes-guides/network/deploying-cilium.md index d4458c86f8..32afe30185 100644 --- a/website/content/v1.5/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.5/kubernetes-guides/network/deploying-cilium.md @@ -302,7 +302,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ## Known issues diff --git a/website/content/v1.6/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.6/kubernetes-guides/network/deploying-cilium.md index 4cf6a35e25..dfd2d1d066 100644 --- a/website/content/v1.6/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.6/kubernetes-guides/network/deploying-cilium.md @@ -273,7 +273,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ## Known issues diff --git a/website/content/v1.7/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.7/kubernetes-guides/network/deploying-cilium.md index 81abb2ff65..25617f5253 100644 --- a/website/content/v1.7/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.7/kubernetes-guides/network/deploying-cilium.md @@ -273,7 +273,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ### Method 5: Using a job diff --git a/website/content/v1.8/kubernetes-guides/network/deploying-cilium.md b/website/content/v1.8/kubernetes-guides/network/deploying-cilium.md index 81abb2ff65..25617f5253 100644 --- a/website/content/v1.8/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.8/kubernetes-guides/network/deploying-cilium.md @@ -273,7 +273,7 @@ As the inline manifest is processed from top to bottom make sure to manually put - Only add the Cilium inline manifest to the control plane nodes machine configuration. - Make sure all control plane nodes have an identical configuration. - If you delete any of the generated resources they will be restored whenever a control plane node reboots. -- As a safety messure Talos only creates missing resources from inline manifests, it never deletes or updates anything. +- As a safety measure, Talos only creates missing resources from inline manifests, it never deletes or updates anything. - If you need to update a manifest make sure to first edit all control plane machine configurations and then run `talosctl upgrade-k8s` as it will take care of updating inline manifests. ### Method 5: Using a job