You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/zh/docs/setup/best-practices/certificates.md
+24-19Lines changed: 24 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,24 +6,25 @@ content_type: concept
6
6
weight: 40
7
7
---
8
8
<!--
9
-
---
10
9
title: PKI certificates and requirements
11
10
reviewers:
12
11
- sig-cluster-lifecycle
13
12
content_type: concept
14
13
weight: 40
15
-
---
16
14
-->
17
15
18
16
<!-- overview -->
19
17
20
18
<!--
21
19
Kubernetes requires PKI certificates for authentication over TLS.
22
20
If you install Kubernetes with [kubeadm](/docs/reference/setup-tools/kubeadm/kubeadm/), the certificates that your cluster requires are automatically generated.
23
-
You can also generate your own certificates -- for example, to keep your private keys more secure by not storing them on the API server.
21
+
You can also generate your own certificates - for example, to keep your private keys more secure by not storing them on the API server.
24
22
This page explains the certificates that your cluster requires.
`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/).
63
63
-->
64
-
只有当您运行 kube-proxy 并要支持[扩展 API 服务器](/docs/tasks/access-kubernetes-api/setup-extension-api-server/)时，才需要 `front-proxy` 证书
64
+
{{< note >}}
65
+
只有当你运行 kube-proxy 并要支持
66
+
[扩展 API 服务器](/zh/docs/tasks/extend-kubernetes/setup-extension-api-server/)
67
+
时，才需要 `front-proxy` 证书
65
68
{{< /note >}}
66
69
67
70
<!--
@@ -146,9 +149,12 @@ Required certificates:
146
149
147
150
where `kind` maps to one or more of the [x509 key usage][usage] types:
148
151
-->
149
-
[1]: 用来连接到集群的不同 IP 或 DNS 名（就像 [kubeadm][kubeadm] 为负载均衡所使用的固定 IP 或 DNS 名，`kubernetes`、`kubernetes.default`、`kubernetes.default.svc`、`kubernetes.default.svc.cluster`、`kubernetes.default.svc.cluster.local`）
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/).
Copy file name to clipboardExpand all lines: content/zh/docs/setup/best-practices/cluster-large.md
+16-11Lines changed: 16 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,7 +42,9 @@ A cluster is a set of nodes (physical or virtual machines) running Kubernetes ag
42
42
<!--
43
43
Normally the number of nodes in a cluster is controlled by the value `NUM_NODES` in the platform-specific `config-default.sh` file (for example, see [GCE's `config-default.sh`](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/gce/config-default.sh)).
Simply changing that value to something very large, however, may cause the setup script to fail for many cloud providers. A GCE deployment, for example, will run in to quota issues and fail to bring the cluster up.
@@ -175,7 +177,9 @@ On AWS, master node sizes are currently set at cluster startup time and do not c
175
177
<!--
176
178
To prevent memory leaks or other resource issues in [cluster addons](https://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons) from consuming all the resources available on a node, Kubernetes sets resource limits on addon containers to limit the CPU and Memory resources they can consume (See PR [#10653](http://pr.k8s.io/10653/files) and [#10778](http://pr.k8s.io/10778/files)).
For directions on how to detect if addon containers are hitting resource limits, see the [Troubleshooting section of Compute Resources](/docs/concepts/configuration/manage-compute-resources-container/#troubleshooting).
In the [future](http://issue.k8s.io/13048), we anticipate to set all cluster addon resource limits based on cluster size, and to dynamically adjust them if you grow or shrink your cluster.
0 commit comments