Merge pull request #40268 from yulng/task19

[zh] content/zh-cn/docs/reference/setup-tools/kubeadm/generated/ task19
pull/40055/head^2
Kubernetes Prow Robot 2023-03-23 07:12:32 -07:00 committed by GitHub
commit ac175e35e0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 36 additions and 3 deletions

View File

@ -13,6 +13,10 @@ Commands related to handling kubernetes certificates
-->
处理 Kubernetes 证书相关的命令
```
kubeadm certs [flags]
```
<!--
### Options
-->

View File

@ -3,7 +3,7 @@ The file is auto-generated from the Go source code of the component using a gene
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
To update the reference content, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.

View File

@ -83,6 +83,20 @@ kubeadm init phase certs apiserver-kubelet-client [flags]
</td>
</tr>
<tr>
<td colspan="2">--dry-run</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Don't apply any changes; just output what would be done.
-->
<p>
不做任何更改;只输出将要执行的操作。
</p>
</td>
</tr>
<tr>
<td colspan="2">-h, --help</td>
</tr>

View File

@ -43,6 +43,20 @@ kubeadm init phase kubelet-finalize experimental-cert-rotation [flags]
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>kubeadm 配置文件的路径。</p></td>
</tr>
<tr>
<td colspan="2">--dry-run</td>
</tr>
<tr>
<td></td><td style="line-height: 130%; word-wrap: break-word;">
<!--
Don't apply any changes; just output what would be done.
-->
<p>
不做任何更改;只输出将要执行的操作。
</p>
</td>
</tr>
<tr>
<td colspan="2">-h, --help</td>
</tr>

View File

@ -3,11 +3,11 @@ The file is auto-generated from the Go source code of the component using a gene
[generator](https://github.com/kubernetes-sigs/reference-docs/). To learn how
to generate the reference documentation, please read
[Contributing to the reference documentation](/docs/contribute/generate-ref-docs/).
To update the reference conent, please follow the
To update the reference content, please follow the
[Contributing upstream](/docs/contribute/generate-ref-docs/contribute-upstream/)
guide. You can file document formatting bugs against the
[reference-docs](https://github.com/kubernetes-sigs/reference-docs/) project.
-->
--
<!--
Upgrade the control plane instance deployed on this node, if any
@ -113,6 +113,7 @@ Path to a directory that contains files named "target[suffix][+patchtype].extens
-->
包含名为 "target[suffix][+patchtype].extension" 的文件的目录的路径。
例如,"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
"target" 可以是 "kube-apiserver"、"kube-controller-manager"、"kube-scheduler"、"etcd"、"kubeletconfiguration" 之一。
"patchtype" 可以是 "strategic"、"merge" 或 "json" 之一,并且它们与 kubectl 支持的补丁格式匹配。
默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
"suffix" 是一个可选字符串,可用于确定首先按字母顺序应用哪些补丁。