You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -164,7 +164,7 @@ Following are the steps for generating a GMSA credential spec YAML manually in J
164
164
The following YAML configuration describes a GMSA credential spec named `gmsa-WebApp1`:
165
165
166
166
```yaml
167
-
apiVersion: windows.k8s.io/v1alpha1
167
+
apiVersion: windows.k8s.io/v1
168
168
kind: GMSACredentialSpec
169
169
metadata:
170
170
name: gmsa-WebApp1 #This is an arbitrary name but it will be used as a reference
@@ -410,7 +410,12 @@ If you are having difficulties getting GMSA to work in your environment, there a
410
410
<!--
411
411
First, make sure the credspec has been passed to the Pod. To do this you will need to `exec` into one of your Pods and check the output of the `nltest.exe /parentdomain` command.
`nltest.exe /parentdomain` results in the following error:
422
427
-->
423
428
`nltest.exe /parentdomain`导致以下错误:
429
+
424
430
```output
425
431
Getting parent domain failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE
426
432
```
@@ -454,6 +460,15 @@ If the DNS and communication test passes, next you will need to check if the Pod
454
460
nltest.exe /query
455
461
```
456
462
463
+
<!--
464
+
Results in the following output:
465
+
-->
466
+
结果输出如下:
467
+
468
+
```output
469
+
I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE
470
+
```
471
+
457
472
<!--
458
473
This tells us that for some reason, the Pod was unable to logon to the domain using the account specified in the credspec. You can try to repair the secure channel by running the following:
0 commit comments