Skip to content

Commit 2df0642

Browse files
authored
Merge pull request #44775 from asa3311/sync-zh-95
[zh] sync configure-service-account horizontal-pod-autoscale-walkthrough install-kubectl-macos
2 parents 833bd95 + 602a2e0 commit 2df0642

File tree

3 files changed

+16
-7
lines changed

3 files changed

+16
-7
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -303,7 +303,7 @@ token might be shorter, or could even be longer).
303303

304304
<!--
305305
When the `ServiceAccountTokenNodeBinding` and `ServiceAccountTokenNodeBindingValidation`
306-
features are enabled and the `KUBECTL_NODE_BOUND_TOKENS` enviroment variable is set to `true`,
306+
features are enabled and the `KUBECTL_NODE_BOUND_TOKENS` environment variable is set to `true`,
307307
it is possible to create a service account token that is directly bound to a `Node`:
308308
-->
309309
当启用了 `ServiceAccountTokenNodeBinding` 和 `ServiceAccountTokenNodeBindingValidation`
@@ -315,7 +315,7 @@ KUBECTL_NODE_BOUND_TOKENS=true kubectl create token build-robot --bound-object-k
315315
```
316316

317317
<!--
318-
The token will be valid until it expires or either the assocaited `Node` or service account are deleted.
318+
The token will be valid until it expires or either the associated `Node` or service account are deleted.
319319
-->
320320
此令牌将有效直至其过期或关联的 `Node` 或服务账户被删除。
321321

@@ -476,7 +476,7 @@ Next, verify it has been created. For example:
476476
所描述的,生成一个镜像拉取 Secret:
477477
478478
```shell
479-
kubectl create secret docker-registry myregistrykey --docker-server=DUMMY_SERVER \
479+
kubectl create secret docker-registry myregistrykey --docker-server=<registry name> \
480480
--docker-username=DUMMY_USERNAME --docker-password=DUMMY_DOCKER_PASSWORD \
481481
--docker-email=DUMMY_DOCKER_EMAIL
482482
```
@@ -578,7 +578,7 @@ ServiceAccount, the new Pod has its `spec.imagePullSecrets` field set automatica
578578
新 Pod 的 `spec.imagePullSecrets` 会被自动设置。
579579

580580
```shell
581-
kubectl run nginx --image=nginx --restart=Never
581+
kubectl run nginx --image=<registry name>/nginx --restart=Never
582582
kubectl get pod nginx -o=jsonpath='{.spec.imagePullSecrets[0].name}{"\n"}'
583583
```
584584

content/zh-cn/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,15 @@ Kubernetes Metrics Server 从集群中的 {{<glossary_tooltip term_id="kubelet"
8989
要了解如何部署 Metrics Server,请参阅
9090
[metrics-server 文档](https://github.com/kubernetes-sigs/metrics-server#deployment)
9191

92+
<!--
93+
If you are running {{< glossary_tooltip term_id="minikube" >}}, run the following command to enable metrics-server:
94+
-->
95+
如果你正在运行 {{< glossary_tooltip term_id="minikube" >}},运行以下命令以启用 metrics-server:
96+
97+
```shell
98+
minikube addons enable metrics-server
99+
```
100+
92101
<!-- steps -->
93102

94103
<!--

content/zh-cn/docs/tasks/tools/install-kubectl-macos.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -195,12 +195,12 @@ The following methods exist for installing kubectl on macOS:
195195
```
196196

197197
<!--
198-
1. After installing the plugin, clean up the installation files:
198+
1. After installing and validating kubectl, delete the checksum file:
199199
-->
200-
1. 安装插件后,清理安装文件
200+
1. 安装并验证 kubectl 后,删除校验和文件
201201

202202
```bash
203-
rm kubectl kubectl.sha256
203+
rm kubectl.sha256
204204
```
205205
<!--
206206
### Install with Homebrew on macOS

0 commit comments

Comments
 (0)