From 8e17234d93e4cba34bf705197cb24c1f587435c7 Mon Sep 17 00:00:00 2001 From: Jan Safranek Date: Tue, 19 Nov 2024 10:03:28 +0100 Subject: [PATCH] Mention MountOption as the default --- .../en/docs/tasks/configure-pod-container/security-context.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/configure-pod-container/security-context.md b/content/en/docs/tasks/configure-pod-container/security-context.md index 637dde15c2..8bd070f9c3 100644 --- a/content/en/docs/tasks/configure-pod-container/security-context.md +++ b/content/en/docs/tasks/configure-pod-container/security-context.md @@ -715,7 +715,7 @@ For Pods that want to opt-out from relabeling using mount options, they can set when multiple pods share a single volume on the same node, but they run with different SELinux labels that allows simultaneous access to the volume. For example, a privileged pod running with label `spc_t` and an unprivileged pod running with the default label `container_file_t`. -With unset `spec.securityContext.seLinuxChangePolicy` (or with the value `MountOption`), +With unset `spec.securityContext.seLinuxChangePolicy` (or with the default value `MountOption`), only one of such pods is able to run on a node, the other one gets ContainerCreating with error `conflicting SELinux labels of volume :