From 357e5a62f0f88f524933f3ff7966dac30fc590b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20=C5=A0afr=C3=A1nek?= Date: Fri, 14 Apr 2023 15:49:42 +0200 Subject: [PATCH] Update content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md Co-authored-by: Tim Bannister --- .../blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md b/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md index d9a3a8806401c..c9f437a4806a7 100644 --- a/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md +++ b/content/en/blog/_posts/2023-04-18-efficient-selinux-relabeling-beta.md @@ -11,7 +11,7 @@ slug: kubernetes-1-27-efficient-selinux-relabeling-beta On Linux with Security-Enhanced Linux (SELinux) enabled, it's traditionally the container runtime that applies SELinux labels to a Pod and all its volumes. -Kubernetes only provides the SELinux label from Pod's Security Context fields +Kubernetes only passes the SELinux label from a Pod's `securityContext` fields to the container runtime. The container runtime then recursively changes SELinux label on all files that