Skip to content

Commit 9d70250

Browse files
authored
Merge pull request #35554 from yanrongshi/zh-cn]Sync-configure-gmsa.md
[zh-cn]Sync configure-gmsa.md
2 parents 00bc3bb + 9ab6ab2 commit 9d70250

File tree

1 file changed

+18
-3
lines changed

1 file changed

+18
-3
lines changed

content/zh-cn/docs/tasks/configure-pod-container/configure-gmsa.md

Lines changed: 18 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ The [YAML template](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/
102102
来部署和配置上述 GMSA Webhook 及相关联的对象。你还可以在运行脚本时设置 `--dry-run=server`
103103
选项以便审查脚本将会对集群做出的变更。
104104

105-
脚本所使用的[YAML 模板](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/admission-webhook/deploy/gmsa-webhook.yml.tpl)
105+
脚本所使用的 [YAML 模板](https://github.com/kubernetes-sigs/windows-gmsa/blob/master/admission-webhook/deploy/gmsa-webhook.yml.tpl)
106106
也可用于手动部署 Webhook 及相关联的对象,不过需要对其中的参数作适当替换。
107107

108108
<!-- steps -->
@@ -164,7 +164,7 @@ Following are the steps for generating a GMSA credential spec YAML manually in J
164164
The following YAML configuration describes a GMSA credential spec named `gmsa-WebApp1`:
165165
166166
```yaml
167-
apiVersion: windows.k8s.io/v1alpha1
167+
apiVersion: windows.k8s.io/v1
168168
kind: GMSACredentialSpec
169169
metadata:
170170
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
410410
<!--
411411
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.
412412
-->
413-
首先,确保 credspec 已传递给 Pod。为此,你需要先运行 `exec` 进入到你的一个 Pod 中并检查 `nltest.exe /parentdomain` 命令的输出。
413+
首先,确保 credspec 已传递给 Pod。为此,你需要先运行 `exec`
414+
进入到你的一个 Pod 中并检查 `nltest.exe /parentdomain` 命令的输出。
415+
416+
<!--
417+
In the example below the Pod did not get the credspec correctly:
418+
-->
414419
在下面的例子中,Pod 未能正确地获得凭据规约:
415420

416421
```PowerShell
@@ -421,6 +426,7 @@ kubectl exec -it iis-auth-7776966999-n5nzr powershell.exe
421426
`nltest.exe /parentdomain` results in the following error:
422427
-->
423428
`nltest.exe /parentdomain` 导致以下错误:
429+
424430
```output
425431
Getting parent domain failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE
426432
```
@@ -454,6 +460,15 @@ If the DNS and communication test passes, next you will need to check if the Pod
454460
nltest.exe /query
455461
```
456462

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+
457472
<!--
458473
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:
459474
-->

0 commit comments

Comments
 (0)