Component reference for 1.22
This commit is contained in:
@@ -69,7 +69,7 @@ control-plane-prepare Prepare the machine for serving a control plane
|
||||
kubelet-start Write kubelet settings, certificates and (re)start the kubelet
|
||||
control-plane-join Join a machine as a control plane instance
|
||||
/etcd Add a new local etcd member
|
||||
/update-status Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap
|
||||
/update-status Register the new control-plane node into the ClusterStatus maintained in the kubeadm-config ConfigMap (DEPRECATED)
|
||||
/mark-control-plane Mark a node as a control-plane
|
||||
```
|
||||
|
||||
@@ -157,13 +157,6 @@ kubeadm join [api-server-endpoint] [flags]
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.</p></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--experimental-patches string</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>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.</p></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">-h, --help</td>
|
||||
</tr>
|
||||
@@ -185,6 +178,13 @@ kubeadm join [api-server-endpoint] [flags]
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Specify the node name.</p></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--patches string</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd". "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.</p></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td colspan="2">--skip-phases strings</td>
|
||||
</tr>
|
||||
|
||||
Reference in New Issue
Block a user