Merge pull request #35609 from yanrongshi/zh-cn]-update-kms-provider.md

[zh-cn]Sync kms-provider.md

Author: k8s-ci-robot

content/zh-cn/docs/tasks/administer-cluster/kms-provider.md

@@ -9,7 +9,9 @@ title: Using a KMS provider for data encryption
 content_type: task
 -->
 <!-- overview -->
-<!-- This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption. -->
+<!--
+This page shows how to configure a Key Management Service (KMS) provider and plugin to enable secret data encryption.
+-->
 
 本页展示了如何配置秘钥管理服务—— Key Management Service (KMS) 驱动和插件以启用
 Secret 数据加密。
@@ -18,8 +20,10 @@ Secret 数据加密。
 
 * {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
 
-<!-- * Kubernetes version 1.10.0 or later is required -->
-<!-- * etcd v3 or later is required -->
+<!--
+* Kubernetes version 1.10.0 or later is required
+* etcd v3 or later is required
+-->
 * 需要 Kubernetes 1.10.0 或更新版本
 * 需要 etcd v3 或更新版本
 
@@ -28,47 +32,59 @@ Secret 数据加密。
 <!-- steps -->
 
 <!--
-The KMS encryption provider uses an envelope encryption scheme to encrypt data in etcd. The data is encrypted using a data encryption key (DEK); a new DEK is generated for each encryption. The DEKs are encrypted with a key encryption key (KEK) that is stored and managed in a remote KMS. The KMS provider uses gRPC to communicate with a specific KMS 
-plugin. The KMS plugin, which is implemented as a gRPC server and deployed on the same host(s) as the Kubernetes master(s), is responsible for all communication with the remote KMS.
+The KMS encryption provider uses an envelope encryption scheme to encrypt data in etcd.
+The data is encrypted using a data encryption key (DEK); a new DEK is generated for each encryption.
+The DEKs are encrypted with a key encryption key (KEK) that is stored and managed in a remote KMS.
+The KMS provider uses gRPC to communicate with a specific KMS plugin.
+The KMS plugin, which is implemented as a gRPC server and deployed on the same host(s)
+as the Kubernetes control plane, is responsible for all communication with the remote KMS.
 -->
 KMS 加密驱动使用封套加密模型来加密 etcd 中的数据。
 数据使用数据加密秘钥（DEK）加密；每次加密都生成一个新的 DEK。
 这些 DEK 经一个秘钥加密秘钥（KEK）加密后在一个远端的 KMS 中存储和管理。
 KMS 驱动使用 gRPC 与一个特定的 KMS 插件通信。这个 KMS 插件作为一个 gRPC 
-服务器被部署在 Kubernetes 主服务器的同一个主机上，负责与远端 KMS 的通信。
+服务器被部署在 Kubernetes 控制平面的相同主机上，负责与远端 KMS 的通信。
 
 <!--
 ## Configuring the KMS provider
 
-To configure a KMS provider on the API server, include a provider of type ```kms``` in the providers array in the encryption configuration file and set the following properties:
+To configure a KMS provider on the API server, include a provider of type `kms` in the
+`providers` array in the encryption configuration file and set the following properties:
 -->
-## 配置 KMS 驱动
+## 配置 KMS 驱动   {#configuring-the-kms-provider}
 
-为了在 API 服务器上配置 KMS 驱动，在加密配置文件中的驱动数组中加入一个类型为 `kms`
+为了在 API 服务器上配置 KMS 驱动，在加密配置文件中的 `providers` 数组中加入一个类型为 `kms`
 的驱动，并设置下列属性：
 
 <!--
 * `name`: Display name of the KMS plugin.
 * `endpoint`: Listen address of the gRPC server (KMS plugin). The endpoint is a UNIX domain socket.
-* `cachesize`: Number of data encryption keys (DEKs) to be cached in the clear. When cached, DEKs can be used without another call to the KMS; whereas DEKs that are not cached require a call to the KMS to unwrap.
-* `timeout`: How long should kube-apiserver wait for kms-plugin to respond before returning an error (default is 3 seconds).
+* `cachesize`: Number of data encryption keys (DEKs) to be cached in the clear.
+  When cached, DEKs can be used without another call to the KMS;
+  whereas DEKs that are not cached require a call to the KMS to unwrap.
+* `timeout`: How long should `kube-apiserver` wait for kms-plugin to respond before
+  returning an error (default is 3 seconds).
 -->
 
 * `name`: KMS 插件的显示名称。
 * `endpoint`: gRPC 服务器（KMS 插件）的监听地址。该端点是一个 UNIX 域套接字。
 * `cachesize`: 以明文缓存的数据加密秘钥（DEKs）的数量。一旦被缓存，
   就可以直接使用 DEKs 而无需另外调用 KMS；而未被缓存的 DEKs 需要调用一次 KMS 才能解包。
-* `timeout`: 在返回一个错误之前，kube-apiserver 等待 kms-plugin 响应的时间（默认是 3 秒）。
+* `timeout`: 在返回一个错误之前，`kube-apiserver` 等待 kms-plugin 响应的时间（默认是 3 秒）。
 
-<!-- See [Understanding the encryption at rest configuration.](/docs/tasks/administer-cluster/encrypt-data) -->
-参见[理解静态数据加密配置](/zh-cn/docs/tasks/administer-cluster/encrypt-data)
+<!--
+See [Understanding the encryption at rest configuration.](/docs/tasks/administer-cluster/encrypt-data)
+-->
+参见[理解静态配置加密](/zh-cn/docs/tasks/administer-cluster/encrypt-data)
 
 <!--
 ## Implementing a KMS plugin
 
-To implement a KMS plugin, you can develop a new plugin gRPC server or enable a KMS plugin already provided by your cloud provider. You then integrate the plugin with the remote KMS and deploy it on the Kubernetes master.
+To implement a KMS plugin, you can develop a new plugin gRPC server or enable a KMS plugin
+already provided by your cloud provider.
+You then integrate the plugin with the remote KMS and deploy it on the Kubernetes master.
 -->
-## 实现 KMS 插件
+## 实现 KMS 插件   {#implementing-a-kms-plugin}
 
 为实现一个 KMS 插件，你可以开发一个新的插件 gRPC 服务器或启用一个由你的云服务驱动提供的 KMS 插件。
 你可以将这个插件与远程 KMS 集成，并把它部署到 Kubernetes 的主服务器上。
@@ -77,46 +93,51 @@ To implement a KMS plugin, you can develop a new plugin gRPC server or enable a
 ### Enabling the KMS supported by your cloud provider 
 Refer to your cloud provider for instructions on enabling the cloud provider-specific KMS plugin.
 -->
-### 启用由云服务驱动支持的 KMS
+### 启用由云服务驱动支持的 KMS   {#enabling-the-kms-supported-by-your-cloud-provider}
 
 有关启用云服务驱动特定的 KMS 插件的说明，请咨询你的云服务驱动商。
 
 <!--
 ### Developing a KMS plugin gRPC server
 
-You can develop a KMS plugin gRPC server using a stub file available for Go. For other languages, you use a proto file to create a stub file that you can use to develop the gRPC server code.
+You can develop a KMS plugin gRPC server using a stub file available for Go. For other languages,
+you use a proto file to create a stub file that you can use to develop the gRPC server code.
 -->
-### 开发 KMS 插件 gRPC 服务器
+### 开发 KMS 插件 gRPC 服务器   {#developing-a-kms-plugin-grpc-server}
 
 你可以使用 Go 语言的存根文件开发 KMS 插件 gRPC 服务器。
 对于其他语言，你可以用 proto 文件创建可以用于开发 gRPC 服务器代码的存根文件。
 
 <!--
 * Using Go: Use the functions and data structures in the stub file:
-[service.pb.go](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.pb.go) to develop the gRPC server code
+  [service.pb.go](https://github.com/kubernetes/kubernetes/blob/release-1.24/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.pb.go)
+  to develop the gRPC server code
 -->
-* 使用 Go：使用存根文件 [service.pb.go](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.pb.go)
+* 使用 Go：使用存根文件 [service.pb.go](https://github.com/kubernetes/kubernetes/blob/release-1.24/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.pb.go)
   中的函数和数据结构开发 gRPC 服务器代码。
 
 <!--
-* Using languages other than Go: Use the protoc compiler with the proto file: [service.proto](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.proto) to generate a stub file for the specific language
+* Using languages other than Go: Use the protoc compiler with the proto file:
+  [service.proto](https://github.com/kubernetes/kubernetes/blob/release-1.24/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.proto)
+  to generate a stub file for the specific language
 -->
 * 使用 Go 以外的其他语言：用 protoc 编译器编译 proto 文件：
-  [service.proto](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.proto)
+  [service.proto](https://github.com/kubernetes/kubernetes/blob/release-1.24/staging/src/k8s.io/apiserver/pkg/storage/value/encrypt/envelope/v1beta1/service.proto)
   为指定语言生成存根文件。
 
 <!--
 Then use the functions and data structures in the stub file to develop the server code.
 -->
 然后使用存根文件中的函数和数据结构开发服务器代码。
 
-<!-- **Notes:** -->
+<!--
+**Notes:**
+-->
 **注意：**
 
 <!--
 * kms plugin version: `v1beta1`
-
-  In response to procedure call Version, a compatible KMS plugin should return v1beta1 as VersionResponse.version.
+  In response to procedure call Version, a compatible KMS plugin should return `v1beta1` as `VersionResponse.version`.
 
 * message version: `v1beta1`
 
@@ -128,7 +149,7 @@ Then use the functions and data structures in the stub file to develop the serve
 -->
 * kms 插件版本：`v1beta1`
 
-  作为对过程调用 Version 的响应，兼容的 KMS 插件应把 v1beta1 作为 VersionResponse.version 返回
+  作为对过程调用 Version 的响应，兼容的 KMS 插件应把 `v1beta1` 作为 `VersionResponse.version` 版本返回。
 
 * 消息版本：`v1beta1`
 
@@ -143,9 +164,10 @@ Then use the functions and data structures in the stub file to develop the serve
 
 The KMS plugin can communicate with the remote KMS using any protocol supported by the KMS.
 All configuration data, including authentication credentials the KMS plugin uses to communicate with the remote KMS, 
-are stored and managed by the KMS plugin independently. The KMS plugin can encode the ciphertext with additional metadata that may be required before sending it to the KMS for decryption.
+are stored and managed by the KMS plugin independently.
+The KMS plugin can encode the ciphertext with additional metadata that may be required before sending it to the KMS for decryption.
 -->
-### 将 KMS 插件与远程 KMS 整合
+### 将 KMS 插件与远程 KMS 整合   {#integrating-a-kms-plugin-with-the-remote-kms}
 
 KMS 插件可以用任何受 KMS 支持的协议与远程 KMS 通信。
 所有的配置数据，包括 KMS 插件用于与远程 KMS 通信的认证凭据，都由 KMS 插件独立地存储和管理。
@@ -156,7 +178,7 @@ KMS 插件可以用额外的元数据对密文进行编码，这些元数据是
 
 Ensure that the KMS plugin runs on the same host(s) as the Kubernetes master(s).
 -->
-### 部署 KMS 插件
+### 部署 KMS 插件   {#deploying-the-kms-plugin}
 
 确保 KMS 插件与 Kubernetes 主服务器运行在同一主机上。
 
@@ -165,7 +187,7 @@ Ensure that the KMS plugin runs on the same host(s) as the Kubernetes master(s).
 
 To encrypt the data:
 -->
-## 使用 KMS 驱动加密数据
+## 使用 KMS 驱动加密数据   {#encrypting-your-data-with-the-kms-provider}
 
 为了加密数据：
 
@@ -175,8 +197,8 @@ To encrypt the data:
 1. 使用 `kms` 驱动的相应的属性创建一个新的加密配置文件：
 
    ```yaml
-   kind: EncryptionConfiguration
    apiVersion: apiserver.config.k8s.io/v1
+   kind: EncryptionConfiguration
    resources:
      - resources:
        - secrets
@@ -190,54 +212,65 @@ To encrypt the data:
    ```
 
 <!--
-2. Set the `--encryption-provider-config` flag on the kube-apiserver to point to the location of the configuration file.
-3. Restart your API server.
+1. Set the `--encryption-provider-config` flag on the kube-apiserver to point to
+   the location of the configuration file.
+1. Restart your API server.
 -->
 2. 设置 kube-apiserver 的 `--encryption-provider-config` 参数指向配置文件的位置。
 3. 重启 API 服务器。
 
+<!--
+For details about the `EncryptionConfiguration` format, please check the
+[API server encryption API reference](/docs/reference/config-api/apiserver-encryption.v1/).
+-->
+有关 `EncryptionConfiguration` 格式的更多详细信息，请参阅
+[kube-apiserver 加密 API 参考 (v1)](/zh-cn/docs/reference/config-api/apiserver-encryption.v1/).
+
 <!--
 ## Verifying that the data is encrypted
 
-Data is encrypted when written to etcd. After restarting your kube-apiserver, any newly created or updated secret should be encrypted when stored. To verify, you can use the etcdctl command line program to retrieve the contents of your secret.
+Data is encrypted when written to etcd. After restarting your `kube-apiserver`, 
+any newly created or updated secret should be encrypted when stored. To verify,
+you can use the `etcdctl` command line program to retrieve the contents of your secret.
 -->
-## 验证数据已经加密
+## 验证数据已经加密    {#verifying-that-the-data-is-encrypted}
 
-写入 etcd 时数据被加密。重启 kube-apiserver 后，任何新建或更新的 Secret 在存储时应该已被加密。
-要验证这点，你可以用 etcdctl 命令行程序获取 Secret 内容。 
+写入 etcd 时数据被加密。重启 `kube-apiserver` 后，任何新建或更新的 Secret 在存储时应该已被加密。
+要验证这点，你可以用 `etcdctl` 命令行程序获取 Secret 内容。 
 
 <!--
-1. Create a new secret called secret1 in the default namespace:
+1. Create a new secret called `secret1` in the `default` namespace:
 -->
-1. 在默认的命名空间里创建一个名为 secret1 的 Secret：
+1. 在默认的命名空间里创建一个名为 `secret1` 的 Secret：
 
    ```
    kubectl create secret generic secret1 -n default --from-literal=mykey=mydata
    ```
 
 <!--
-2. Using the etcdctl command line, read that secret out of etcd:
+1. Using the `etcdctl` command line, read that secret out of etcd:
 -->
-2. 用 etcdctl 命令行，从 etcd 读取出 Secret：
+2. 用 `etcdctl` 命令行，从 etcd 读取出 Secret：
 
    ```
    ETCDCTL_API=3 etcdctl get /kubernetes.io/secrets/default/secret1 [...] | hexdump -C
    ```
 
    <!--
-   where `[...]` must be the additional arguments for connecting to the etcd server.
+   where `[...]` contains the additional arguments for connecting to the etcd server.
    -->
-   其中 `[...]` 是用于连接 etcd 服务器的额外参数。
+   其中 `[...]` 包含连接 etcd 服务器的额外参数。
 
 <!--
-3. Verify the stored secret is prefixed with `k8s:enc:kms:v1:`, which indicates that the `kms` provider has encrypted the resulting data.
+1. Verify the stored secret is prefixed with `k8s:enc:kms:v1:`, which indicates that
+   the `kms` provider has encrypted the resulting data.
 -->
 3. 验证保存的 Secret 是否是以 `k8s:enc:kms:v1:` 开头的，这表明 `kms` 驱动已经对结果数据加密。
 
 <!--
-4. Verify that the secret is correctly decrypted when retrieved via the API:
+1. Verify that the secret is correctly decrypted when retrieved via the API:
 -->
-4. 验证 Secret 在被 API 获取时已被正确解密：
+4. 验证通过 API 获取的 Secret 已被正确解密：
 
    ```
    kubectl describe secret secret1 -n default
@@ -250,12 +283,13 @@ Data is encrypted when written to etcd. After restarting your kube-apiserver, an
 
 Because secrets are encrypted on write, performing an update on a secret encrypts that content.
 -->
-## 确保所有 Secret 都已被加密
+## 确保所有 Secret 都已被加密    {#ensuring-all-secrets-are-encrypted}
 
 因为 Secret 是在写入时被加密的，所以在更新 Secret 时也会加密该内容。
 
 <!--
-The following command reads all secrets and then updates them to apply server side encryption. If an error occurs due to a conflicting write, retry the command.
+The following command reads all secrets and then updates them to apply server side encryption.
+If an error occurs due to a conflicting write, retry the command.
 For larger clusters, you may wish to subdivide the secrets by namespace or script an update.
 -->
 下列命令读取所有 Secret 并更新它们以便应用服务器端加密。如果因为写入冲突导致错误发生，
@@ -270,7 +304,7 @@ kubectl get secrets --all-namespaces -o json | kubectl replace -f -
 
 To switch from a local encryption provider to the `kms` provider and re-encrypt all of the secrets:
 -->
-## 从本地加密驱动切换到 KMS 驱动
+## 从本地加密驱动切换到 KMS 驱动    {#switching-from-a-local-encryption-provider-to-the-kms-provider}
 
 为了从本地加密驱动切换到 `kms` 驱动并重新加密所有 Secret 内容：
 
@@ -280,8 +314,8 @@ To switch from a local encryption provider to the `kms` provider and re-encrypt
 1. 在配置文件中加入 `kms` 驱动作为第一个条目，如下列样例所示
 
    ```yaml
-   kind: EncryptionConfiguration
    apiVersion: apiserver.config.k8s.io/v1
+   kind: EncryptionConfiguration
    resources:
      - resources:
        - secrets
@@ -297,21 +331,21 @@ To switch from a local encryption provider to the `kms` provider and re-encrypt
    ```
 
 <!--
-2. Restart all kube-apiserver processes.
-3. Run the following command to force all secrets to be re-encrypted using the `kms` provider.
+1. Restart all `kube-apiserver` processes.
+1. Run the following command to force all secrets to be re-encrypted using the `kms` provider.
 -->
-2. 重启所有 kube-apiserver 进程。
+2. 重启所有 `kube-apiserver` 进程。
 3. 运行下列命令使用 `kms` 驱动强制重新加密所有 Secret。
 
    ```
-   kubectl get secrets --all-namespaces -o json| kubectl replace -f -
+   kubectl get secrets --all-namespaces -o json | kubectl replace -f -
    ```
 
 <!--
 ## Disabling encryption at rest
 To disable encryption at rest:
 -->
-## 禁用静态数据加密
+## 禁用静态数据加密   {#disabling-encryption-at-rest}
 
 要禁用静态数据加密：
 
@@ -321,8 +355,8 @@ To disable encryption at rest:
 1. 将 `identity` 驱动作为配置文件中的第一个条目： 
 
    ```yaml
-   kind: EncryptionConfiguration
    apiVersion: apiserver.config.k8s.io/v1
+   kind: EncryptionConfiguration
    resources:
      - resources:
        - secrets
@@ -335,10 +369,10 @@ To disable encryption at rest:
    ```
 
 <!--
-2.  Restart all kube-apiserver processes.
-3. Run the following command to force all secrets to be decrypted.
+1. Restart all `kube-apiserver` processes.
+1. Run the following command to force all secrets to be decrypted.
 -->
-2. 重启所有 kube-apiserver 进程。
+2. 重启所有 `kube-apiserver` 进程。
 3. 运行下列命令强制重新加密所有 Secret。
 
    ```