@@ -18,40 +18,42 @@ The "init" command executes the following phases:
1818"init" 命令执行以下阶段：
1919
2020```
21- preflight Run pre-flight checks
22- kubelet-start Write kubelet settings and (re)start the kubelet
23- certs Certificate generation
24- /ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
25- /apiserver Generate the certificate for serving the Kubernetes API
26- /apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet
27- /front-proxy-ca Generate the self-signed CA to provision identities for front proxy
28- /front-proxy-client Generate the certificate for the front proxy client
29- /etcd-ca Generate the self-signed CA to provision identities for etcd
30- /etcd-server Generate the certificate for serving etcd
31- /etcd-peer Generate the certificate for etcd nodes to communicate with each other
32- /etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd
33- /apiserver-etcd-client Generate the certificate the apiserver uses to access etcd
34- /sa Generate a private key for signing service account tokens along with its public key
35- kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
36- /admin Generate a kubeconfig file for the admin to use and for kubeadm itself
37- /kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
38- /controller-manager Generate a kubeconfig file for the controller manager to use
39- /scheduler Generate a kubeconfig file for the scheduler to use
40- control-plane Generate all static Pod manifest files necessary to establish the control plane
41- /apiserver Generates the kube-apiserver static Pod manifest
42- /controller-manager Generates the kube-controller-manager static Pod manifest
43- /scheduler Generates the kube-scheduler static Pod manifest
44- etcd Generate static Pod manifest file for local etcd
45- /local Generate the static Pod manifest file for a local, single-node local etcd instance
46- upload-config Upload the kubeadm and kubelet configuration to a ConfigMap
47- /kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
48- /kubelet Upload the kubelet component config to a ConfigMap
49- upload-certs Upload certificates to kubeadm-certs
50- mark-control-plane Mark a node as a control-plane
51- bootstrap-token Generates bootstrap tokens used to join a node to a cluster
52- addon Install required addons for passing Conformance tests
53- /coredns Install the CoreDNS addon to a Kubernetes cluster
54- /kube-proxy Install the kube-proxy addon to a Kubernetes cluster
21+ preflight Run pre-flight checks
22+ certs Certificate generation
23+ /ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components
24+ /apiserver Generate the certificate for serving the Kubernetes API
25+ /apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet
26+ /front-proxy-ca Generate the self-signed CA to provision identities for front proxy
27+ /front-proxy-client Generate the certificate for the front proxy client
28+ /etcd-ca Generate the self-signed CA to provision identities for etcd
29+ /etcd-server Generate the certificate for serving etcd
30+ /etcd-peer Generate the certificate for etcd nodes to communicate with each other
31+ /etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd
32+ /apiserver-etcd-client Generate the certificate the apiserver uses to access etcd
33+ /sa Generate a private key for signing service account tokens along with its public key
34+ kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file
35+ /admin Generate a kubeconfig file for the admin to use and for kubeadm itself
36+ /kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes
37+ /controller-manager Generate a kubeconfig file for the controller manager to use
38+ /scheduler Generate a kubeconfig file for the scheduler to use
39+ kubelet-start Write kubelet settings and (re)start the kubelet
40+ control-plane Generate all static Pod manifest files necessary to establish the control plane
41+ /apiserver Generates the kube-apiserver static Pod manifest
42+ /controller-manager Generates the kube-controller-manager static Pod manifest
43+ /scheduler Generates the kube-scheduler static Pod manifest
44+ etcd Generate static Pod manifest file for local etcd
45+ /local Generate the static Pod manifest file for a local, single-node local etcd instance
46+ upload-config Upload the kubeadm and kubelet configuration to a ConfigMap
47+ /kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap
48+ /kubelet Upload the kubelet component config to a ConfigMap
49+ upload-certs Upload certificates to kubeadm-certs
50+ mark-control-plane Mark a node as a control-plane
51+ bootstrap-token Generates bootstrap tokens used to join a node to a cluster
52+ kubelet-finalize Updates settings relevant to the kubelet after TLS bootstrap
53+ /experimental-cert-rotation Enable kubelet client certificate rotation
54+ addon Install required addons for passing Conformance tests
55+ /coredns Install the CoreDNS addon to a Kubernetes cluster
56+ /kube-proxy Install the kube-proxy addon to a Kubernetes cluster
5557```
5658
5759```
@@ -190,14 +192,18 @@ Don't apply any changes; just output what would be done.
190192</tr >
191193
192194<tr >
193- <td colspan =" 2 " >-k, -- experimental-kustomize string</td >
195+ <td colspan =" 2 " >-- experimental-patches string</td >
194196</tr >
195197<tr >
196198<td ></td ><td style =" line-height 130% ; word-wrap break-word ;" >
197- <!--
198- The path where kustomize patches for static pod manifests are stored.
199- -->
200- 用于存储 kustomize 为静态 pod 清单所提供的补丁的路径。
199+ <!--
200+ Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically.
201+ -->
202+ 包含名为 "target[ suffix] [ +patchtype ] .extension" 的文件的目录路径。
203+ 例如，"kube-apiserver0+merge.yaml" 或仅仅是 "etcd.json"。
204+ "patchtype" 可以是 "strategic"、"merge" 或 "json" 之一，并且它们与 kubectl 支持的补丁格式匹配。
205+ 默认的 "patchtype" 为 "strategic"。 "extension" 必须为 "json" 或 "yaml"。
206+ "suffix" 是一个可选字符串，可用于确定首先按字母顺序应用哪些补丁。
201207</td >
202208</tr >
203209
0 commit comments