From 8cdf0f7cb007790190197356355a16c8e427afab Mon Sep 17 00:00:00 2001 From: darox Date: Wed, 24 Apr 2024 13:54:03 +0200 Subject: [PATCH] docs: fix typo in Cilium instructions Use correct pod security label. Signed-off-by: darox Signed-off-by: Andrey Smirnov --- .../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 +- 3 files changed, 3 insertions(+), 3 deletions(-) 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 0b4bc06eab..455091e3ba 100644 --- a/website/content/v1.6/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.6/kubernetes-guides/network/deploying-cilium.md @@ -292,7 +292,7 @@ For more details: [GCP ILB support / support scope local routes to be configured ```Error creating: pods "client-69748f45d8-9b9jg" is forbidden: violates PodSecurity "baseline:latest": non-default capabilities (container "client" must not include "NET_RAW" in securityContext.capabilities.add)``` - This is expected, you can workaround it by adding the `pod-security.kubernetes.io/enforce=priviledged` [label on the namespace level]({{< relref "../configuration/pod-security">}}). + This is expected, you can workaround it by adding the `pod-security.kubernetes.io/enforce=privileged` [label on the namespace level]({{< relref "../configuration/pod-security">}}). - Talos has full kernel module support for eBPF, See: - [Cilium System Requirements](https://docs.cilium.io/en/v1.14/operations/system_requirements/) 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 0b4bc06eab..455091e3ba 100644 --- a/website/content/v1.7/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.7/kubernetes-guides/network/deploying-cilium.md @@ -292,7 +292,7 @@ For more details: [GCP ILB support / support scope local routes to be configured ```Error creating: pods "client-69748f45d8-9b9jg" is forbidden: violates PodSecurity "baseline:latest": non-default capabilities (container "client" must not include "NET_RAW" in securityContext.capabilities.add)``` - This is expected, you can workaround it by adding the `pod-security.kubernetes.io/enforce=priviledged` [label on the namespace level]({{< relref "../configuration/pod-security">}}). + This is expected, you can workaround it by adding the `pod-security.kubernetes.io/enforce=privileged` [label on the namespace level]({{< relref "../configuration/pod-security">}}). - Talos has full kernel module support for eBPF, See: - [Cilium System Requirements](https://docs.cilium.io/en/v1.14/operations/system_requirements/) 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 0b4bc06eab..455091e3ba 100644 --- a/website/content/v1.8/kubernetes-guides/network/deploying-cilium.md +++ b/website/content/v1.8/kubernetes-guides/network/deploying-cilium.md @@ -292,7 +292,7 @@ For more details: [GCP ILB support / support scope local routes to be configured ```Error creating: pods "client-69748f45d8-9b9jg" is forbidden: violates PodSecurity "baseline:latest": non-default capabilities (container "client" must not include "NET_RAW" in securityContext.capabilities.add)``` - This is expected, you can workaround it by adding the `pod-security.kubernetes.io/enforce=priviledged` [label on the namespace level]({{< relref "../configuration/pod-security">}}). + This is expected, you can workaround it by adding the `pod-security.kubernetes.io/enforce=privileged` [label on the namespace level]({{< relref "../configuration/pod-security">}}). - Talos has full kernel module support for eBPF, See: - [Cilium System Requirements](https://docs.cilium.io/en/v1.14/operations/system_requirements/)