Windows: Adds RunAsUserName related documentation (#15378)
Recently, the RunAsUserName feature has been added, allowing users to run Windows containers with custom usernames, different from the image default usernames. Adds documentation regarding its prerequisites, feature gate, usage, restrictions, and samples.
This commit is contained in:
committed by
Kubernetes Prow Robot
parent
128e9c26b0
commit
98533bdfb9
@@ -104,6 +104,10 @@ Port mapping is also supported, but for simplicity in this example the container
|
||||
Windows container hosts are not able to access the IP of services scheduled on them due to current platform limitations of the Windows networking stack. Only Windows pods are able to access service IPs.
|
||||
{{< /note >}}
|
||||
|
||||
## Using configurable Container usernames
|
||||
|
||||
Starting with Kubernetes v1.16, Windows containers can be configured to run their entrypoints and processes with different usernames than the image defaults. The way this is achieved is a bit different from the way it is done for Linux containers. Learn more about it [here](/docs/tasks/configure-pod-container/configure-runasusername/).
|
||||
|
||||
## Managing Workload Identity with Group Managed Service Accounts
|
||||
|
||||
Starting with Kubernetes v1.14, Windows container workloads can be configured to use Group Managed Service Accounts (GMSA). Group Managed Service Accounts are a specific type of Active Directory account that provides automatic password management, simplified service principal name (SPN) management, and the ability to delegate the management to other administrators across multiple servers. Containers configured with a GMSA can access external Active Directory Domain resources while carrying the identity configured with the GMSA. Learn more about configuring and using GMSA for Windows containers [here](/docs/tasks/configure-pod-container/configure-gmsa/).
|
||||
|
||||
Reference in New Issue
Block a user