whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update supported container runtimes in configure-gmsa.md

Browse Source
This commit is contained in:
Mark Rossetti
2022-01-19 14:57:16 -08:00
parent d2b9f0e09c
commit f13522be29
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-gmsa.md
+2 -2
View File
@@ -10,7 +10,7 @@ weight: 20
This page shows how to configure [Group Managed Service Accounts](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview) (GMSA) for Pods and containers that will run on Windows nodes. 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. This page shows how to configure [Group Managed Service Accounts](https://docs.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview) (GMSA) for Pods and containers that will run on Windows nodes. 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.
In Kubernetes, GMSA credential specs are configured at a Kubernetes cluster-wide scope as Custom Resources. Windows Pods, as well as individual containers within a Pod, can be configured to use a GMSA for domain based functions (e.g. Kerberos authentication) when interacting with other Windows services. As of v1.16, the Docker runtime supports GMSA for Windows workloads. In Kubernetes, GMSA credential specs are configured at a Kubernetes cluster-wide scope as Custom Resources. Windows Pods, as well as individual containers within a Pod, can be configured to use a GMSA for domain based functions (e.g. Kerberos authentication) when interacting with other Windows services.
## {{% heading "prerequisites" %}} ## {{% heading "prerequisites" %}}
@@ -66,7 +66,7 @@ Following are the steps for generating a GMSA credential spec YAML manually in J
The following YAML configuration describes a GMSA credential spec named `gmsa-WebApp1`: The following YAML configuration describes a GMSA credential spec named `gmsa-WebApp1`:
```yaml ```yaml
apiVersion: windows.k8s.io/v1alpha1 apiVersion: windows.k8s.io/v1
kind: GMSACredentialSpec kind: GMSACredentialSpec
metadata: metadata:
name: gmsa-WebApp1 #This is an arbitrary name but it will be used as a reference name: gmsa-WebApp1 #This is an arbitrary name but it will be used as a reference