Skip to content

Updating runAsNonRoot support for Windows #30256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k8s-ci-robot merged 1 commit into from
Oct 29, 2021
Merged

Updating runAsNonRoot support for Windows #30256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions ...ent/en/docs/setup/production-environment/windows/intro-windows-in-kubernetes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down