Skip to content

Commit afbb133

Browse files
committed
Updating runAsNonRoot support for Windows
Signed-off-by: Mark Rossetti <[email protected]>
1 parent 2cf8506 commit afbb133

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -526,13 +526,13 @@ work between Windows and Linux:
526526
* `securityContext.readOnlyRootFilesystem` -
527527
not possible on Windows; write access is required for registry & system
528528
processes to run inside the container
529-
* `EcurityContext.runAsGroup` -
529+
* `securityContext.runAsGroup` -
530530
not possible on Windows as there is no GID support
531-
* `ecurityContext.runAsNonRoot` -
532-
Windows does not have a root user. The closest equivalent is `ContainerAdministrator`
533-
which is an identity that doesn't exist on the node.
531+
* `securityContext.runAsNonRoot` -
532+
this setting will prevent containers from running as `ContainerAdministrator`
533+
which is the closest equivalent to a root user on Windows.
534534
* `securityContext.runAsUser` -
535-
use [`runAsUsername`](/docs/tasks/configure-pod-container/configure-runasusername)
535+
use [`runAsUserName`](/docs/tasks/configure-pod-container/configure-runasusername)
536536
instead
537537
* `securityContext.seLinuxOptions` -
538538
not possible on Windows as SELinux is Linux-specific

0 commit comments

Comments
 (0)