kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #43129 from asa3311/sync-zh-64 

[zh] sync dns-debugging-resolution kubeadm-certs reserve-compute-resources
pull/43163/head
Kubernetes Prow Robot 2023-09-22 05:26:48 -07:00 committed by GitHub
parent 9c66f01bee 0d7885eb4c
commit 7b11b1998f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 13 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
content/zh-cn/docs/tasks/administer-cluster/dns-debugging-resolution.md
View File

@ -545,14 +545,14 @@ Linux 的 libc（又名 glibc）默认将 DNS `nameserver` 记录限制为 3，
你也可以使用 kubelet 的 `--resolv-conf` 标志来解决这个问题。
<!--
If you are using Alpine version 3.3 or earlier as your base image, DNS may not
work properly due to a known issue with Alpine.
Kubernetes [issue 30215](https://github.com/kubernetes/kubernetes/issues/30215)
details more information on this.
If you are using Alpine version 3.17 or earlier as your base image, DNS may not
work properly due to a design issue with Alpine.
Until musl version 1.24 didn't include TCP fallback to the DNS stub resolver meaning any DNS call above 512 bytes would fail.
Please upgrade your images to Alpine version 3.18 or above.
-->
如果你使用 Alpine 3.3 或更早版本作为你的基础镜像，DNS 可能会由于 Alpine 中
一个已知的问题导致无法正常工作。
请查看[这里](https://github.com/kubernetes/kubernetes/issues/30215)获取更多信息。
如果你使用 Alpine 3.17 或更早版本作为你的基础镜像，DNS 可能会由于 Alpine 的设计问题而无法工作。
在 musl 1.24 版本之前，DNS 存根解析器都没有包括 TCP 回退，
这意味着任何超过 512 字节的 DNS 调用都会失败。请将你的镜像升级到 Alpine 3.18 或更高版本。
## {{% heading "whatsnext" %}}

5
content/zh-cn/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md
View File

@ -297,7 +297,10 @@ kubeadm certs renew all
{{< note >}}
<!--
Clusters built with kubeadm often copy the `admin.conf` certificate into `$HOME/.kube/config`, as instructed in [Creating a cluster with kubeadm](https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/). On such a system, to update the contents of `$HOME/.kube/config` after renewing the `admin.conf` you must run the following commands:
Clusters built with kubeadm often copy the `admin.conf` certificate into
`$HOME/.kube/config`, as instructed in [Creating a cluster with kubeadm](/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/).
On such a system, to update the contents of `$HOME/.kube/config`
after renewing the `admin.conf`, you must run the following commands:
-->
使用 kubeadm 构建的集群通常会将 `admin.conf` 证书复制到 `$HOME/.kube/config` 中，
如[使用 kubeadm 创建集群](/zh-cn/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/)中所指示的那样。

4
content/zh-cn/docs/tasks/administer-cluster/reserve-compute-resources.md
View File

@ -251,10 +251,10 @@ with `.slice` appended.
<!--
**Kubelet Flag**: `--reserved-cpus=0-3`
**KubeletConfiguration Flag**: `reservedSystemCpus: 0-3`
**KubeletConfiguration Flag**: `reservedSystemCPUs: 0-3`
-->
**Kubelet 标志**: `--reserved-cpus=0-3`
**KubeletConfiguration 标志**：`reservedSystemCpus: 0-3`
**KubeletConfiguration 标志**：`reservedSystemCPUs: 0-3`
<!--
`reserved-cpus` is meant to define an explicit CPU set for OS system daemons and