From afbb133e9f5ab7e9ac7a10ffa8cb229c94dc590a Mon Sep 17 00:00:00 2001 From: Mark Rossetti Date: Tue, 26 Oct 2021 13:25:31 -0700 Subject: [PATCH] Updating runAsNonRoot support for Windows Signed-off-by: Mark Rossetti --- .../windows/intro-windows-in-kubernetes.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md index fa8733bbb7..5b1400c49e 100644 --- a/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md +++ b/content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md @@ -526,13 +526,13 @@ work between Windows and Linux: * `securityContext.readOnlyRootFilesystem` - not possible on Windows; write access is required for registry & system processes to run inside the container -* `EcurityContext.runAsGroup` - +* `securityContext.runAsGroup` - not possible on Windows as there is no GID support -* `ecurityContext.runAsNonRoot` - - Windows does not have a root user. The closest equivalent is `ContainerAdministrator` - which is an identity that doesn't exist on the node. +* `securityContext.runAsNonRoot` - + this setting will prevent containers from running as `ContainerAdministrator` + which is the closest equivalent to a root user on Windows. * `securityContext.runAsUser` - - use [`runAsUsername`](/docs/tasks/configure-pod-container/configure-runasusername) + use [`runAsUserName`](/docs/tasks/configure-pod-container/configure-runasusername) instead * `securityContext.seLinuxOptions` - not possible on Windows as SELinux is Linux-specific