[zh] Remove reviewer for kubeadm

content/zh/docs/reference/setup-tools/kubeadm/kubeadm-join.md

@@ -1,12 +1,17 @@
 ---
+title: kubeadm join
+content_type: concept
+weight: 30
+---
+<!--
 reviewers:
-- mikedanese
 - luxas
 - jbeda
 title: kubeadm join
 content_type: concept
 weight: 30
----
+-->
+
 <!-- overview -->
 <!--
 This command initializes a Kubernetes worker node and joins it to the cluster.
@@ -23,11 +28,11 @@ This command initializes a Kubernetes worker node and joins it to the cluster.
 ### join 工作流 {#join-workflow}
 
 <!--
-`kubeadm join` bootstraps a Kubernetes worker node and joins it to the cluster.
+`kubeadm join` bootstraps a Kubernetes worker node or a control-plane node and adds it to the cluster.
-This action consists of the following steps:
+This action consists of the following steps for worker nodes:
 -->
-`kubeadm join` 初始化 Kubernetes 工作节点并将其加入集群。
+`kubeadm join` 初始化 Kubernetes 工作节点或控制平面节点并将其添加到集群中。
-该操作过程包含下面几个步骤：
+对于工作节点，该操作包括以下步骤：
 
 <!--
 1. kubeadm downloads necessary cluster information from the API server.
@@ -110,7 +115,7 @@ command, `kubeadm join phase` allows you to skip a list of phases using the `--s
 
 For example:
 -->
-类似于 [kubeadm init phase](/zh/docs/reference/setup-tools/kubeadm/kubeadm-init/#init-phases)命令，
+类似于 [kubeadm init phase](/zh/docs/reference/setup-tools/kubeadm/kubeadm-init/#init-phases) 命令，
 `kubeadm join phase` 允许你使用 `--skip-phases` 标志跳过阶段列表。
 
 例如：
@@ -129,7 +134,7 @@ Alternatively, you can use the `skipPhases` field in `JoinConfiguration`.
 <!--
 ### Discovering what cluster CA to trust
 -->
-### 发现要信任的集群 CA
+### 发现要信任的集群 CA {#discovering-what-cluster-ca-to-trust}
 
 <!--
 The kubeadm discovery has several options, each with security tradeoffs.
@@ -143,16 +148,16 @@ Kubeadm 的发现有几个选项，每个选项都有安全性上的优缺点。
 <!--
 #### Token-based discovery with CA pinning
 -->
-#### 带 CA 锁定模式的基于令牌的发现
+#### 带 CA 锁定模式的基于令牌的发现 {#token-based-discovery-with-ca-pinning}
 
 <!--
-This is the default mode in Kubernetes 1.8 and above. In this mode, kubeadm downloads
+This is the default mode in kubeadm. In this mode, kubeadm downloads
 the cluster configuration (including root CA) and validates it using the token
 as well as validating that the root CA public key matches the provided hash and
 that the API server certificate is valid under the root CA.
 -->
-这是 Kubernetes 1.8 及以上版本中的默认模式。
+这是 kubeadm 的默认模式。
-在这种模式下，kubeadm 下载集群配置（包括根CA）并使用令牌验证它，
+在这种模式下，kubeadm 下载集群配置（包括根 CA）并使用令牌验证它，
 并且会验证根 CA 的公钥与所提供的哈希是否匹配，
 以及 API 服务器证书在根 CA 下是否有效。
 
@@ -162,7 +167,7 @@ The CA key hash has the format `sha256:<hex_encoded_hash>`. By default, the hash
 CA 键哈希格式为 `sha256:<hex_encoded_hash>`。
 默认情况下，在 `kubeadm init` 最后打印的 `kubeadm join` 命令
 或者 `kubeadm token create --print-join-command` 的输出信息中返回哈希值。
-它使用标准格式 (请参考 [RFC7469](https://tools.ietf.org/html/rfc7469#section-2.4)) 
+它使用标准格式（请参考 [RFC7469](https://tools.ietf.org/html/rfc7469#section-2.4)）
 并且也能通过第三方工具或者制备系统进行计算。
 例如，使用 OpenSSL CLI：
 
@@ -171,7 +176,7 @@ openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outfor
 ```
 
 <!--
-**Example `kubeadm join` command:**
+**Example `kubeadm join` commands:**
 -->
 **`kubeadm join` 命令示例**
 
@@ -204,52 +209,52 @@ if the `kubeadm init` command was called with `--upload-certs`.
 <!--
 **Advantages:**
 
- - Allows bootstrapping nodes to securely discover a root of trust for the
+- Allows bootstrapping nodes to securely discover a root of trust for the
-   master even if other worker nodes or the network are compromised.
+  control-plane node even if other worker nodes or the network are compromised.
 
- - Convenient to execute manually since all of the information required fits
+- Convenient to execute manually since all of the information required fits
-   into a single `kubeadm join` command.
+  into a single `kubeadm join` command.
 -->
 
 **优势：**
 
-- 允许引导节点安全地发现主节点的信任根，即使其他工作节点或网络受到损害。
+- 允许引导节点安全地发现控制平面节点的信任根，即使其他工作节点或网络受到损害。
 
 - 方便手动执行，因为所需的所有信息都可放到一个 `kubeadm join` 命令中。
 
 <!--
 **Disadvantages:**
 
-- The CA hash is not normally known until the master has been provisioned,
+- The CA hash is not normally known until the control-plane node has been provisioned,
   which can make it more difficult to build automated provisioning tools that
   use kubeadm. By generating your CA in beforehand, you may workaround this
-  limitation though.
+  limitation.
 -->
 
 **劣势：**
 
-- CA 哈希通常在主节点被提供之前是不知道的，这使得构建使用 kubeadm 的自动化配置工具更加困难。
+- CA 哈希通常在控制平面节点被提供之前是不知道的，这使得构建使用 kubeadm 的自动化配置工具更加困难。
-  通过预先生成CA，你可以解除这个限制。
+  通过预先生成 CA，你可以解除这个限制。
 
 <!--
 #### Token-based discovery without CA pinning
 -->
-#### 无 CA 锁定模式的基于令牌的发现
+#### 无 CA 锁定模式的基于令牌的发现 {#token-based-discovery-without-ca-pinning}
 
 <!--
-_This was the default in Kubernetes 1.7 and earlier_, but comes with some
+This mode relies only on the symmetric token to sign
-important caveats. This mode relies only on the symmetric token to sign
 (HMAC-SHA256) the discovery information that establishes the root of trust for
-the master. It's still possible in Kubernetes 1.8 and above using the
+the control-plane. To use the mode the joining nodes must skip the hash validation of the
-`--discovery-token-unsafe-skip-ca-verification` flag, but you should consider
+CA public key, using `--discovery-token-unsafe-skip-ca-verification`. You should consider
 using one of the other modes if possible.
 
 **Example `kubeadm join` command:**
 -->
-_这是 Kubernetes 1.7 和早期版本_中的默认设置；使用时要注意一些重要的补充说明。
+此模式仅依靠对称令牌来签署 (HMAC-SHA256) 为控制平面建立信任根的发现信息。
-此模式仅依赖于对称令牌来签名(HMAC-SHA256)发现信息，这些发现信息为主节点建立信任根。
+要使用该模式，加入节点必须使用
-在 Kubernetes 1.8 及以上版本中仍然可以使用 `--discovery-token-unsafe-skip-ca-verification`
+`--discovery-token-unsafe-skip-ca-verification`
-参数，但是如果可能的话，你应该考虑使用一种其他模式。
+跳过 CA 公钥的哈希验证。
+如果可以，你应该考虑使用其他模式。
 
 **`kubeadm join` 命令示例**
 
@@ -262,7 +267,7 @@ kubeadm join --token abcdef.1234567890abcdef --discovery-token-unsafe-skip-ca-ve
 
 - Still protects against many network-level attacks.
 
-- The token can be generated ahead of time and shared with the master and
+- The token can be generated ahead of time and shared with the control-plane node and
   worker nodes, which can then bootstrap in parallel without coordination. This
   allows it to be used in many provisioning scenarios.
 -->
@@ -271,7 +276,7 @@ kubeadm join --token abcdef.1234567890abcdef --discovery-token-unsafe-skip-ca-ve
 
 - 仍然可以防止许多网络级攻击。
 
-- 可以提前生成令牌并与主节点和工作节点共享，这样主节点和工作节点就可以并行引导而无需协调。
+- 可以提前生成令牌并与控制平面节点和工作节点共享，这样控制平面节点和工作节点就可以并行引导而无需协调。
   这允许它在许多配置场景中使用。
 
 <!--
@@ -279,20 +284,20 @@ kubeadm join --token abcdef.1234567890abcdef --discovery-token-unsafe-skip-ca-ve
 
 - If an attacker is able to steal a bootstrap token via some vulnerability,
   they can use that token (along with network-level access) to impersonate the
-  master to other bootstrapping nodes. This may or may not be an appropriate
+  control-plane node to other bootstrapping nodes. This may or may not be an appropriate
   tradeoff in your environment.
 -->
 
 **劣势**
 
 - 如果攻击者能够通过某些漏洞窃取引导令牌，那么他们可以使用该令牌（连同网络级访问）
-  为其它处于引导过程中的节点提供假冒的主节点。
+  为其它处于引导过程中的节点提供假冒的控制平面节点。
   在你的环境中，这可能是一个适当的折衷方法，也可能不是。
 
 <!--
 #### File or HTTPS-based discovery
 -->
-#### 基于 HTTPS 或文件发现
+#### 基于 HTTPS 或文件发现 {#file-or-https-based-discovery}
 
 <!--
 This provides an out-of-band way to establish a root of trust between the control-plane node
@@ -302,7 +307,7 @@ using kubeadm. The format of the discovery file is a regular Kubernetes
 
 In case the discovery file does not contain credentials, the TLS discovery token will be used.
 -->
-这种方案提供了一种带外方式在主节点和引导节点之间建立信任根。
+这种方案提供了一种带外方式在控制平面节点和引导节点之间建立信任根。
 如果使用 kubeadm 构建自动配置，请考虑使用此模式。
 发现文件的格式为常规的 Kubernetes
 [kubeconfig](/zh/docs/tasks/access-application-cluster/configure-access-multiple-clusters/) 文件。
@@ -314,35 +319,40 @@ In case the discovery file does not contain credentials, the TLS discovery token
 -->
 **`kubeadm join` 命令示例：**
 
-- `kubeadm join --discovery-file path/to/file.conf` （本地文件）
+<!--
+- `kubeadm join --discovery-file path/to/file.conf` (local file)
 
-- `kubeadm join --discovery-file https://url/file.conf` (远程 HTTPS URL)
+- `kubeadm join --discovery-file https://url/file.conf` (remote HTTPS URL)
+-->
+- `kubeadm join --discovery-file path/to/file.conf`（本地文件）
+
+- `kubeadm join --discovery-file https://url/file.conf`（远程 HTTPS URL）
 
 <!--
 **Advantages:**
 
 - Allows bootstrapping nodes to securely discover a root of trust for the
-  master even if the network or other worker nodes are compromised.
+  control-plane node even if the network or other worker nodes are compromised.
 -->
 
 **优势：**
 
-- 允许引导节点安全地发现主节点的信任根，即使网络或其他工作节点受到损害。
+- 允许引导节点安全地发现控制平面节点的信任根，即使网络或其他工作节点受到损害。
 
 <!--
 **Disadvantages:**
 
 - Requires that you have some way to carry the discovery information from
-  the master to the bootstrapping nodes. This might be possible, for example,
+  the control-plane node to the bootstrapping nodes. If the discovery file contains credentials
-  via your cloud provider or provisioning tool. The information in this file is
+  you must keep it secret and transfer it over a secure channel. This might be possible with your
-  not secret, but HTTPS or equivalent is required to ensure its integrity.
+  cloud provider or provisioning tool.
 -->
 
 **劣势：**
 
-- 要求你有某种方法将发现信息从主节点传送到引导节点。
+- 要求你有某种方法将发现信息从控制平面节点传送到引导节点。
-  例如，这可以通过云提供商或驱动工具实现。
+  如果发现文件包含凭据，你必须对其保密并通过安全通道进行传输。
-  该文件中的信息不是加密的，而是需要 HTTPS 或等效文件来保证其完整性。
+  这可能通过你的云提供商或供应工具来实现。
 
 <!--
 ### Securing your installation even more {#securing-more}
@@ -359,7 +369,7 @@ Kubeadm 的默认值可能不适用于所有人。
 <!--
 #### Turning off auto-approval of node client certificates
 -->
-#### 关闭节点客户端证书的自动批准
+#### 关闭节点客户端证书的自动批准 {#turning-off-auto-approval-of-node-client-certificates}
 
 <!--
 By default, there is a CSR auto-approver enabled that basically approves any client certificate request
@@ -423,22 +433,21 @@ node-csr-c69HXe7aYcqkS1bKmH4faEnHAWxn6i2bHZ2mD04jZyQ   1m        system:bootstra
 <!--
 This forces the workflow that `kubeadm join` will only succeed if `kubectl certificate approve` has been run.
 -->
-这迫使工作流只有在运行了 kubectl 证书批准后，kubeadm join 才能成功。
+这迫使工作流只有在运行了 `kubectl certificate approve` 后，`kubeadm join` 才能成功。
 
 <!--
 #### Turning off public access to the cluster-info ConfigMap
 -->
-#### 关闭对集群信息 ConfigMap 的公开访问
+#### 关闭对集群信息 ConfigMap 的公开访问 {#turning-off-public-access-to-the-cluster-info-configmap}
 
 <!--
 In order to achieve the joining flow using the token as the only piece of validation information, a
- ConfigMap with some data needed for validation of the master's identity is exposed publicly by
+ ConfigMap with some data needed for validation of the control-plane node's identity is exposed publicly by
 default. While there is no private data in this ConfigMap, some users might wish to turn
 it off regardless. Doing so will disable the ability to use the `--discovery-token` flag of the
 `kubeadm join` flow. Here are the steps to do so:
 -->
-为了实现使用令牌作为唯一验证信息的加入工作流，默认情况下会公开带有验证主节点标识
+为了实现使用令牌作为唯一验证信息的加入工作流，默认情况下会公开带有验证控制平面节点标识所需数据的 ConfigMap。
-所需数据的 ConfigMap。
 虽然此 ConfigMap 中没有私有数据，但一些用户可能希望无论如何都关闭它。
 这样做需要禁用 `kubeadm join` 工作流的 `--discovery-token` 参数。
 以下是实现步骤：
@@ -488,16 +497,18 @@ users: []
 <!--
 These commands should be run after `kubeadm init` but before `kubeadm join`.
 -->
-这些命令应该在执行 `kubeadm init` 之后、在`kubeadm join` 之前执行。
+这些命令应该在执行 `kubeadm init` 之后、在 `kubeadm join` 之前执行。
 
 <!--
 ### Using kubeadm join with a configuration file {#config-file}
 -->
-### 使用带有配置文件的 kubeadm join
+### 使用带有配置文件的 kubeadm join {#config-file}
 
 {{< caution >}}
-<!--The config file is still considered alpha and may change in future versions.-->
+<!--
-配置文件目前是 alpha 功能，在将来的版本中可能会变动。
+The config file is still considered beta and may change in future versions.
+-->
+配置文件目前是 beta 功能，在将来的版本中可能会变动。
 {{< /caution >}}
 
 <!--
@@ -507,7 +518,7 @@ configuration file options. This file is passed using the `--config` flag and it
 contain a `JoinConfiguration` structure. Mixing `--config` with others flags may not be
 allowed in some cases.
 -->
-可以用配置文件替代命令行参数的方法配置 `kubeadm join`，一些高级功能也只有在使用配置文件时才可选用。
+可以用配置文件替代命令行参数的方法配置 `kubeadm join`，一些进阶功能也只有在使用配置文件时才可选用。
 该文件通过 `--config` 参数来传递，并且文件中必须包含 `JoinConfiguration` 结构。
 在某些情况下，不允许将 `--config` 与其他标志混合使用。
 
@@ -536,12 +547,12 @@ For more information on the fields and usage of the configuration you can naviga
 ## {{% heading "whatsnext" %}}
 
 <!--
-* [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) to bootstrap a Kubernetes master node
+* [kubeadm init](/docs/reference/setup-tools/kubeadm/kubeadm-init/) to bootstrap a Kubernetes control-plane node
 * [kubeadm token](/docs/reference/setup-tools/kubeadm/kubeadm-token/) to manage tokens for `kubeadm join`
 * [kubeadm reset](/docs/reference/setup-tools/kubeadm/kubeadm-reset/) to revert any changes made to this host by `kubeadm init` or `kubeadm join`
 -->
 * [kubeadm init](/zh/docs/reference/setup-tools/kubeadm/kubeadm-init/)
-  初始化 Kubernetes 主节点
+  初始化 Kubernetes 控制平面节点
 * [kubeadm token](/zh/docs/reference/setup-tools/kubeadm/kubeadm-token/)
   管理 `kubeadm join` 的令牌
 * [kubeadm reset](/zh/docs/reference/setup-tools/kubeadm/kubeadm-reset/)