From aa44d74fc9d0162bfa43f1965faf585881ac171e Mon Sep 17 00:00:00 2001
From: 2BFL <imqksl@gmail.com>
Date: Sat, 7 Mar 2020 18:25:34 +0800
Subject: [PATCH] translation certificates for zh (#19492)

Accept tengqm's suggestion
---
 .../docs/setup/best-practices/certificates.md | 285 ++++++++++++++++++
 1 file changed, 285 insertions(+)
 create mode 100644 content/zh/docs/setup/best-practices/certificates.md

diff --git a/content/zh/docs/setup/best-practices/certificates.md b/content/zh/docs/setup/best-practices/certificates.md
new file mode 100644
index 0000000000..0d04a4dbf4
--- /dev/null
+++ b/content/zh/docs/setup/best-practices/certificates.md
@@ -0,0 +1,285 @@
+---
+title: PKI 证书和要求
+reviewers:
+- sig-cluster-lifecycle
+content_template: templates/concept
+weight: 40
+---
+<!--
+---
+title: PKI certificates and requirements
+reviewers:
+- sig-cluster-lifecycle
+content_template: templates/concept
+weight: 40
+---
+-->
+
+{{% capture overview %}}
+
+<!--
+Kubernetes requires PKI certificates for authentication over TLS.
+If you install Kubernetes with [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/), the certificates that your cluster requires are automatically generated.
+You can also generate your own certificates -- for example, to keep your private keys more secure by not storing them on the API server.
+This page explains the certificates that your cluster requires.
+-->
+Kubernetes 需要 PKI 证书才能进行基于 TLS 的身份验证。如果您是使用 [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/) 安装的 Kubernetes，则会自动生成集群所需的证书。您还可以生成自己的证书。例如，不将私钥存储在 API 服务器上，可以让私钥更加安全。此页面说明了集群必需的证书。
+
+{{% /capture %}}
+
+{{% capture body %}}
+
+<!--
+## How certificates are used by your cluster
+
+Kubernetes requires PKI for the following operations:
+-->
+## 集群是如何使用证书的
+
+Kubernetes 需要 PKI 才能执行以下操作：
+
+<!--
+* Client certificates for the kubelet to authenticate to the API server
+* Server certificate for the API server endpoint
+* Client certificates for administrators of the cluster to authenticate to the API server
+* Client certificates for the API server to talk to the kubelets
+* Client certificate for the API server to talk to etcd
+* Client certificate/kubeconfig for the controller manager to talk to the API server
+* Client certificate/kubeconfig for the scheduler to talk to the API server.
+* Client and server certificates for the [front-proxy][proxy]
+-->
+* Kubelet 的客户端证书，用于 API 服务器身份验证
+* API 服务器端点的证书
+* 集群管理员的客户端证书，用于 API 服务器身份认证
+* API 服务器的客户端证书，用于和 Kubelet 的会话
+* API 服务器的客户端证书，用于和 etcd 的会话
+* 控制器管理器的客户端证书/kubeconfig，用于和 API server 的会话
+* 调度器的客户端证书/kubeconfig，用于和 API server 的会话
+* [前端代理][proxy] 的客户端及服务端证书
+
+{{< note >}}
+<!--
+`front-proxy` certificates are required only if you run kube-proxy to support [an extension API server](/docs/tasks/access-kubernetes-api/setup-extension-api-server/).
+-->
+只有当您运行 kube-proxy 并要支持[扩展 API 服务器](/docs/tasks/access-kubernetes-api/setup-extension-api-server/)时，才需要 `front-proxy` 证书
+{{< /note >}}
+
+<!--
+etcd also implements mutual TLS to authenticate clients and peers.
+-->
+etcd 还实现了双向 TLS 来对客户端和对其他对等节点进行身份验证。
+
+<!--
+## Where certificates are stored
+
+If you install Kubernetes with kubeadm, certificates are stored in `/etc/kubernetes/pki`. All paths in this documentation are relative to that directory.
+-->
+## 证书存放的位置
+
+如果你是通过 kubeadm 安装的 Kubernetes，所有证书都存放在 `/etc/kuberntes/pki` 目录下。本文所有相关的路径都是基于该路径的相对路径。
+
+<!--
+## Configure certificates manually
+
+If you don't want kubeadm to generate the required certificates, you can create them in either of the following ways.
+-->
+## 手动配置证书
+
+如果你不想通过 kubeadm 生成这些必需的证书，你可以通过下面两种方式之一来手动创建他们。
+
+<!--
+### Single root CA
+
+You can create a single root CA, controlled by an administrator. This root CA can then create multiple intermediate CAs, and delegate all further creation to Kubernetes itself.
+-->
+### 单根 CA
+
+你可以创建一个单根 CA，由管理员控制器它。该根 CA 可以创建多个中间 CA，并将所有进一步的创建委托给 Kubernetes。
+
+<!--
+Required CAs:
+
+| 路径                    | 默认 CN                    | 描述                             |
+|------------------------|---------------------------|----------------------------------|
+| ca.crt,key             | kubernetes-ca             | Kubernetes general CA            |
+| etcd/ca.crt,key        | etcd-ca                   | For all etcd-related functions   |
+| front-proxy-ca.crt,key | kubernetes-front-proxy-ca | For the [front-end proxy][proxy] |
+
+On top of the above CAs, it is also necessary to get a public/private key pair for service account management, `sa.key` and `sa.pub`.
+-->
+需要这些 CA：
+
+| 路径                    | 默认 CN                    | 描述                             |
+|------------------------|---------------------------|----------------------------------|
+| ca.crt,key             | kubernetes-ca             | Kubernetes 通用 CA                |
+| etcd/ca.crt,key        | etcd-ca                   | 与 etcd 相关的所有功能              |
+| front-proxy-ca.crt,key | kubernetes-front-proxy-ca | 用于 [前端代理][proxy] |
+
+上面的 CA 之外，还需要获取用于服务账户管理的密钥对，也就是 `sa.key` 和 `sa.pub`。
+
+<!--
+### All certificates
+
+If you don't wish to copy the CA private keys to your cluster, you can generate all certificates yourself.
+
+Required certificates:
+-->
+### 所有的证书
+
+如果你不想将 CA 的私钥拷贝至你的集群中，你也可以自己生成全部的证书。
+
+需要这些证书：
+
+| 默认 CN                    | 父级 CA                 | O (位于 Subject 中) | 类型                                   | 主机 (SAN)                                 |
+|-------------------------------|---------------------------|----------------|----------------------------------------|---------------------------------------------|
+| kube-etcd                     | etcd-ca                   |                | server, client                         | `localhost`, `127.0.0.1`                        |
+| kube-etcd-peer                | etcd-ca                   |                | server, client                         | `<hostname>`, `<Host_IP>`, `localhost`, `127.0.0.1` |
+| kube-etcd-healthcheck-client  | etcd-ca                   |                | client                                 |                                             |
+| kube-apiserver-etcd-client    | etcd-ca                   | system:masters | client                                 |                                             |
+| kube-apiserver                | kubernetes-ca             |                | server                                 | `<hostname>`, `<Host_IP>`, `<advertise_IP>`, `[1]` |
+| kube-apiserver-kubelet-client | kubernetes-ca             | system:masters | client                                 |                                             |
+| front-proxy-client            | kubernetes-front-proxy-ca |                | client                                 |                                             |
+
+<!--
+[1]: any other IP or DNS name you contact your cluster on (as used by [kubeadm][kubeadm] the load balancer stable IP and/or DNS name, `kubernetes`, `kubernetes.default`, `kubernetes.default.svc`,
+`kubernetes.default.svc.cluster`, `kubernetes.default.svc.cluster.local`)
+
+where `kind` maps to one or more of the [x509 key usage][usage] types:
+-->
+[1]: 用来连接到集群的不同 IP 或 DNS 名（就像 [kubeadm][kubeadm] 为负载均衡所使用的固定 IP 或 DNS 名，`kubernetes`、`kubernetes.default`、`kubernetes.default.svc`、`kubernetes.default.svc.cluster`、`kubernetes.default.svc.cluster.local`）
+
+其中，`kind` 对应一种或多种类型的 [x509 密钥用途][usage]：
+
+<!--
+| kind   | Key usage                                                                       |
+|--------|---------------------------------------------------------------------------------|
+| server | digital signature, key encipherment, server auth                                |
+| client | digital signature, key encipherment, client auth                                |
+-->
+| kind   | 密钥用途                                                                         |
+|--------|---------------------------------------------------------------------------------|
+| server | 数字签名、密钥加密、服务端认证                                                       |
+| client | 数字签名、密钥加密、客户端认证                                                       |
+
+
+{{< note >}}
+<!--
+Hosts/SAN listed above are the recommended ones for getting a working cluster; if required by a specific setup, it is possible to add additional SANs on all the server certificates.
+-->
+上面列出的 Hosts/SAN 是推荐的配置方式；如果需要特殊安装，则可以在所有服务器证书上添加其他 SAN。
+{{< /note >}}
+
+{{< note >}}
+<!--
+For kubeadm users only:
+
+* The scenario where you are copying to your cluster CA certificates without private keys is referred as external CA in the kubeadm documentation.
+* If you are comparing the above list with a kubeadm generated PKI, please be aware that `kube-etcd`, `kube-etcd-peer` and `kube-etcd-healthcheck-client` certificates
+  are not generated in case of external etcd.
+-->
+对于 kubeadm 用户：
+
+* 不使用私钥，将证书复制到集群 CA 的方案，在 kubeadm 文档中将这种方案称为外部 CA。
+* 如果将以上列表与 kubeadm 生成的 PKI 进行比较，你会注意到，如果使用外部 etcd，则不会生成 `kube-etcd`、`kube-etcd-peer` 和 `kube-etcd-healthcheck-client` 证书。
+
+{{< /note >}}
+
+<!--
+### Certificate paths
+
+Certificates should be placed in a recommended path (as used by [kubeadm][kubeadm]). Paths should be specified using the given argument regardless of location.
+-->
+### 证书路径
+
+证书应放置在建议的路径中（以便 [kubeadm][kubeadm]使用）。无论使用什么位置，都应使用给定的参数指定路径。
+
+| 默认 CN                   | 建议的密钥路径         | 建议的证书路径       | 命令        | 密钥参数               | 证书参数                             |
+|------------------------------|------------------------------|-----------------------------|----------------|------------------------------|-------------------------------------------|
+| etcd-ca                      |     etcd/ca.key                         | etcd/ca.crt                 | kube-apiserver |                              | --etcd-cafile                             |
+| kube-apiserver-etcd-client   | apiserver-etcd-client.key    | apiserver-etcd-client.crt   | kube-apiserver | --etcd-keyfile               | --etcd-certfile                           |
+| kubernetes-ca                |    ca.key                          | ca.crt                      | kube-apiserver |                              | --client-ca-file                          |
+| kubernetes-ca                |    ca.key                          | ca.crt                      | kube-controller-manager | --cluster-signing-key-file      | --client-ca-file, --root-ca-file, --cluster-signing-cert-file  |
+| kube-apiserver               | apiserver.key                | apiserver.crt               | kube-apiserver | --tls-private-key-file       | --tls-cert-file                           |
+| kube-apiserver-kubelet-client|     apiserver-kubelet-client.key                         | apiserver-kubelet-client.crt| kube-apiserver | --kubelet-client-key | --kubelet-client-certificate              |
+| front-proxy-ca               |     front-proxy-ca.key                         | front-proxy-ca.crt          | kube-apiserver |                              | --requestheader-client-ca-file            |
+| front-proxy-ca               |     front-proxy-ca.key                         | front-proxy-ca.crt          | kube-controller-manager |                              | --requestheader-client-ca-file |
+| front-proxy-client           | front-proxy-client.key       | front-proxy-client.crt      | kube-apiserver | --proxy-client-key-file      | --proxy-client-cert-file                  |
+| etcd-ca                      |         etcd/ca.key                     | etcd/ca.crt                 | etcd           |                              | --trusted-ca-file, --peer-trusted-ca-file |
+| kube-etcd                    | etcd/server.key              | etcd/server.crt             | etcd           | --key-file                   | --cert-file                               |
+| kube-etcd-peer               | etcd/peer.key                | etcd/peer.crt               | etcd           | --peer-key-file              | --peer-cert-file                          |
+| etcd-ca                      |                              | etcd/ca.crt                 | etcdctl    |                              | --cacert                                  |
+| kube-etcd-healthcheck-client | etcd/healthcheck-client.key  | etcd/healthcheck-client.crt | etcdctl     | --key                        | --cert                                    |
+
+<!--
+Same considerations apply for the service account key pair:
+-->
+注意事项同样适用于服务帐户密钥对：
+
+| 私钥路径            | 公钥路径            | 命令                 | 参数                             |
+|------------------------------|-----------------------------|-------------------------|--------------------------------------|
+|  sa.key                      |                             | kube-controller-manager | service-account-private              |
+|                              | sa.pub                      | kube-apiserver          | service-account-key                  |
+
+<!--
+## Configure certificates for user accounts
+
+You must manually configure these administrator account and service accounts:
+-->
+## 为用户帐户配置证书
+
+您必须手动配置以下管理员帐户和服务帐户：
+
+| 文件名                | 凭据名称            | 默认 CN                     | O (位于 Subject 中) |
+|-------------------------|----------------------------|--------------------------------|----------------|
+| admin.conf              | default-admin              | kubernetes-admin               | system:masters |
+| kubelet.conf            | default-auth               | system:node:`<nodeName>` (see note) | system:nodes   |
+| controller-manager.conf | default-controller-manager | system:kube-controller-manager |                |
+| scheduler.conf          | default-scheduler          | system:kube-scheduler          |                |
+
+{{< note >}}
+<!--
+The value of `<nodeName>` for `kubelet.conf` **must** match precisely the value of the node name provided by the kubelet as it registers with the apiserver. For further details, read the [Node Authorization](/docs/reference/access-authn-authz/node/).
+-->
+`kubelet.conf` 中 `<nodeName>` 的值 **必须** 与 kubelet 向 apiserver 注册时提供的节点名称的值完全匹配。有关更多详细信息，请阅读[节点授权](/docs/reference/access-authn-authz/node/)。
+{{< /note >}}
+
+<!--
+1. For each config, generate an x509 cert/key pair with the given CN and O.
+
+1. Run `kubectl` as follows for each config:
+-->
+1. 对于每个配置，请都使用给定的 CN 和 O 生成 x509 证书/密钥偶对。
+
+1. 为每个配置运行下面的 `kubectl` 命令：
+
+```shell
+KUBECONFIG=<filename> kubectl config set-cluster default-cluster --server=https://<host ip>:6443 --certificate-authority <path-to-kubernetes-ca> --embed-certs
+KUBECONFIG=<filename> kubectl config set-credentials <credential-name> --client-key <path-to-key>.pem --client-certificate <path-to-cert>.pem --embed-certs
+KUBECONFIG=<filename> kubectl config set-context default-system --cluster default-cluster --user <credential-name>
+KUBECONFIG=<filename> kubectl config use-context default-system
+```
+
+<!--
+These files are used as follows:
+
+| filename                | command                 | comment                                                               |
+|-------------------------|-------------------------|-----------------------------------------------------------------------|
+| admin.conf              | kubectl                 | Configures administrator user for the cluster                                      |
+| kubelet.conf            | kubelet                 | One required for each node in the cluster.                            |
+| controller-manager.conf | kube-controller-manager | Must be added to manifest in `manifests/kube-controller-manager.yaml` |
+| scheduler.conf          | kube-scheduler          | Must be added to manifest in `manifests/kube-scheduler.yaml`          |
+-->
+这些文件用途如下：
+
+| 文件名                   | 命令                     | 说明                                                                  |
+|-------------------------|-------------------------|-----------------------------------------------------------------------|
+| admin.conf              | kubectl                 | 配置集群的管理员                                                         |
+| kubelet.conf            | kubelet                 | 集群中的每个节点都需要一份                                                 |
+| controller-manager.conf | kube-controller-manager | 必需添加到 `manifests/kube-controller-manager.yaml` 清单中               |
+| scheduler.conf          | kube-scheduler          | 必需添加到 `manifests/kube-scheduler.yaml` 清单中                        |
+
+[usage]: https://godoc.org/k8s.io/api/certificates/v1beta1#KeyUsage
+[kubeadm]: /docs/reference/setup-tools/kubeadm/kubeadm/
+[proxy]: /docs/tasks/access-kubernetes-api/configure-aggregation-layer/
+
+{{% /capture %}}