From f0568d42edaef57bc9b2291a58969112f13a692a Mon Sep 17 00:00:00 2001
From: "xin.li" <xin.li@daocloud.io>
Date: Mon, 29 Jan 2024 13:45:41 +0800
Subject: [PATCH] [zh-cn] sync names components hello-minikube

Signed-off-by: xin.li <xin.li@daocloud.io>
---
 .../docs/concepts/overview/components.md      | 28 ++++++---
 .../overview/working-with-objects/names.md    | 13 +++-
 .../zh-cn/docs/tutorials/hello-minikube.md    | 61 ++++++++++++++++---
 3 files changed, 84 insertions(+), 18 deletions(-)

diff --git a/content/zh-cn/docs/concepts/overview/components.md b/content/zh-cn/docs/concepts/overview/components.md
index 059947e521..9e65ad1bc5 100644
--- a/content/zh-cn/docs/concepts/overview/components.md
+++ b/content/zh-cn/docs/concepts/overview/components.md
@@ -25,6 +25,7 @@ card:
 -->
 
 <!-- overview -->
+
 <!--
 When you deploy Kubernetes, you get a cluster.
 {{ < glossary_definition term_id="cluster" length="all" prepend="A Kubernetes cluster consists of">}}
@@ -47,13 +48,16 @@ a complete and working Kubernetes cluster.
 <!--
 ## Control Plane Components
 
-The control plane's components make global decisions about the cluster (for example, scheduling), as well as detecting and responding to cluster events (for example, starting up a new {{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's `replicas` field is unsatisfied).
+The control plane's components make global decisions about the cluster (for example, scheduling),
+as well as detecting and responding to cluster events (for example, starting up a new
+{{< glossary_tooltip text="pod" term_id="pod">}} when a deployment's
+`{{< glossary_tooltip text="replicas" term_id="replica" >}}` field is unsatisfied).
  -->
 ## 控制平面组件（Control Plane Components）    {#control-plane-components}
 
 控制平面组件会为集群做出全局决策，比如资源的调度。
-以及检测和响应集群事件，例如当不满足部署的 `replicas` 字段时，
-要启动新的 {{< glossary_tooltip text="pod" term_id="pod">}}）。
+以及检测和响应集群事件，例如当不满足部署的 `{{< glossary_tooltip text="replicas" term_id="replica" >}}`
+字段时，要启动新的 {{< glossary_tooltip text="Pod" term_id="pod">}}）。
 
 <!--
 Control plane components can be run on any machine in the cluster. However,
@@ -98,7 +102,7 @@ The above is not an exhaustive list.
 有许多不同类型的控制器。以下是一些例子：
 
 * 节点控制器（Node Controller）：负责在节点出现故障时进行通知和响应
-* 任务控制器（Job Controller）：监测代表一次性任务的 Job 对象，然后创建 Pods 来运行这些任务直至完成
+* 任务控制器（Job Controller）：监测代表一次性任务的 Job 对象，然后创建 Pod 来运行这些任务直至完成
 * 端点分片控制器（EndpointSlice controller）：填充端点分片（EndpointSlice）对象（以提供 Service 和 Pod 之间的链接）。
 * 服务账号控制器（ServiceAccount controller）：为新的命名空间创建默认的服务账号（ServiceAccount）。
 
@@ -187,9 +191,11 @@ see [Addons](/docs/concepts/cluster-administration/addons/).
 <!--
 ### DNS
 
-While the other addons are not strictly required, all Kubernetes clusters should have [cluster DNS](/docs/concepts/services-networking/dns-pod-service/), as many examples rely on it.
+While the other addons are not strictly required, all Kubernetes clusters should have
+[cluster DNS](/docs/concepts/services-networking/dns-pod-service/), as many examples rely on it.
 
-Cluster DNS is a DNS server, in addition to the other DNS server(s) in your environment, which serves DNS records for Kubernetes services.
+Cluster DNS is a DNS server, in addition to the other DNS server(s) in your environment,
+which serves DNS records for Kubernetes services.
 
 Containers started by Kubernetes automatically include this DNS server in their DNS searches.
 -->
@@ -206,7 +212,9 @@ Kubernetes 启动的容器自动将此 DNS 服务器包含在其 DNS 搜索列
 <!--
 ### Web UI (Dashboard)
 
-[Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) is a general purpose, web-based UI for Kubernetes clusters. It allows users to manage and troubleshoot applications running in the cluster, as well as the cluster itself.
+[Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/) is a general purpose,
+web-based UI for Kubernetes clusters. It allows users to manage and troubleshoot applications
+running in the cluster, as well as the cluster itself.
 -->
 ### Web 界面（仪表盘）   {#web-ui-dashboard}
 
@@ -218,7 +226,8 @@ Kubernetes 启动的容器自动将此 DNS 服务器包含在其 DNS 搜索列
 <!--
 ### Container Resource Monitoring
 
-[Container Resource Monitoring](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/) records generic time-series metrics
+[Container Resource Monitoring](/docs/tasks/debug/debug-cluster/resource-usage-monitoring/)
+records generic time-series metrics
 about containers in a central database, and provides a UI for browsing that data.
 -->
 ### 容器资源监控   {#container-resource-monitoring}
@@ -254,7 +263,8 @@ allocating IP addresses to pods and enabling them to communicate with each other
 
 <!--
 Learn more about the following:
-   * [Nodes](/docs/concepts/architecture/nodes/) and [their communication](/docs/concepts/architecture/control-plane-node-communication/) with the control plane.
+   * [Nodes](/docs/concepts/architecture/nodes/) and [their communication](/docs/concepts/architecture/control-plane-node-communication/)
+     with the control plane.
    * Kubernetes [controllers](/docs/concepts/architecture/controller/).
    * [kube-scheduler](/docs/concepts/scheduling-eviction/kube-scheduler/) which is the default scheduler for Kubernetes.
    * Etcd's official [documentation](https://etcd.io/docs/).
diff --git a/content/zh-cn/docs/concepts/overview/working-with-objects/names.md b/content/zh-cn/docs/concepts/overview/working-with-objects/names.md
index 579208fb0d..3707bfcae8 100644
--- a/content/zh-cn/docs/concepts/overview/working-with-objects/names.md
+++ b/content/zh-cn/docs/concepts/overview/working-with-objects/names.md
@@ -136,6 +136,17 @@ This means the name must:
 - 必须以字母开头
 - 必须以字母数字结尾
 
+{{< note >}}
+<!--
+The only difference between the RFC 1035 and RFC 1123
+label standards is that RFC 1123 labels are allowed to
+start with a digit, whereas RFC 1035 labels can start
+with a lowercase alphabetic character only.
+-->
+RFC 1035 和 RFC 1123 标签标准之间的唯一区别是 RFC 1123
+标签允许以数字开头，而 RFC 1035 标签只能以小写字母字符开头。
+{{< /note >}}
+
 <!--
 ### Path Segment Names
 
@@ -191,4 +202,4 @@ UUID 是标准化的，见 ISO/IEC 9834-8 和 ITU-T X.667。
 * See the [Identifiers and Names in Kubernetes](https://git.k8s.io/design-proposals-archive/architecture/identifiers.md) design document.
 -->
 * 进一步了解 Kubernetes [标签](/zh-cn/docs/concepts/overview/working-with-objects/labels/)和[注解](/zh-cn/docs/concepts/overview/working-with-objects/annotations/)。
-* 参阅 [Kubernetes 标识符和名称](https://git.k8s.io/design-proposals-archive/architecture/identifiers.md)的设计文档
+* 参阅 [Kubernetes 标识符和名称](https://git.k8s.io/design-proposals-archive/architecture/identifiers.md)的设计文档。
diff --git a/content/zh-cn/docs/tutorials/hello-minikube.md b/content/zh-cn/docs/tutorials/hello-minikube.md
index 82788e32e5..0f0daf8562 100644
--- a/content/zh-cn/docs/tutorials/hello-minikube.md
+++ b/content/zh-cn/docs/tutorials/hello-minikube.md
@@ -51,14 +51,22 @@ The tutorial provides a container image that uses NGINX to echo back all the req
 
 <!--
 This tutorial assumes that you have already set up `minikube`.
-See [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions.
+See __Step 1__ in [minikube start](https://minikube.sigs.k8s.io/docs/start/) for installation instructions.
+-->
+本教程假设你已经安装了 `minikube`。
+有关安装说明，请参阅 [minikube start](https://minikube.sigs.k8s.io/docs/start/) 的**步骤 1**。
 
+{{< note >}}
+<!--
+Only execute the instructions in __Step 1, Installation__. The rest is covered on this page.
+-->
+仅执行**步骤 1：安装**中的说明，其余内容均包含在本页中。
+{{< /note >}}
+
+<!--
 You also need to install `kubectl`.
 See [Install tools](/docs/tasks/tools/#kubectl) for installation instructions.
 -->
-本教程假设你已经安装了 `minikube`。
-有关安装说明，请参阅 [minikube start](https://minikube.sigs.k8s.io/docs/start/)。
-
 你还需要安装 `kubectl`。
 有关安装说明，请参阅[安装工具](/zh-cn/docs/tasks/tools/#kubectl)。
 
@@ -394,7 +402,7 @@ Minikube 有一组内置的{{< glossary_tooltip text="插件" term_id="addons" >
    ```
 
 <!--
-2. Enable an addon, for example, `metrics-server`:
+1. Enable an addon, for example, `metrics-server`:
 -->
 2. 启用插件，例如 `metrics-server`：
 
@@ -413,7 +421,7 @@ Minikube 有一组内置的{{< glossary_tooltip text="插件" term_id="addons" >
    ```
 
 <!--
-3. View the Pod and Service you created by installing that addon:
+1. View the Pod and Service you created by installing that addon:
 -->
 3. 查看通过安装该插件所创建的 Pod 和 Service：
 
@@ -449,9 +457,37 @@ Minikube 有一组内置的{{< glossary_tooltip text="插件" term_id="addons" >
    ```
 
 <!--
-4. Disable `metrics-server`:
+1. Check the output from `metrics-server`:
 -->
-4. 禁用 `metrics-server`：
+4. 检查 `metrics-server` 的输出：
+
+   ```shell
+   kubectl top pods
+   ```
+
+   <!--
+   The output is similar to:
+   -->
+   输出类似于：
+
+   ```
+   NAME                         CPU(cores)   MEMORY(bytes)   
+   hello-node-ccf4b9788-4jn97   1m           6Mi             
+   ```
+
+   <!--
+   If you see the following message, wait, and try again:
+   -->
+   如果你看到以下消息，请等待并重试：
+
+   ```
+   error: Metrics API not available
+   ```
+
+<!--
+1. Disable `metrics-server`:
+--->
+5. 禁用 `metrics-server`：
 
    ```shell
    minikube addons disable metrics-server
@@ -505,6 +541,15 @@ If you want to use minikube again to learn more about Kubernetes, you don't need
 -->
 如果你还想使用 Minikube 进一步学习 Kubernetes，那就不需要删除 Minikube。
 
+<!--
+## Conclusion
+
+This page covered the basic aspects to get a minikube cluster up and running. You are now ready to deploy applications.
+-->
+## 结论
+
+本页介绍了启动和运行 minikube 集群的基本知识，现在部署应用的准备工作已经完成。
+
 ## {{% heading "whatsnext" %}}
 
 <!--