kubeadm_join_phase_control-plane-prepare_all [page]deterministic

### Synopsis

Prepare the machine for serving a control plane

``` kubeadm join phase control-plane-prepare all [api-server-endpoint] [flags] ```

### Options

<table style="width: 100%; table-layout: fixed;"> <colgroup> <col span="1" style="width: 10px;" /> <col span="1" /> </colgroup> <tbody>

<tr> <td colspan="2">--apiserver-advertise-address string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If the node should host a new control plane instance, the IP address the API Server will advertise it's listening on. If not set the default network interface will be used.</p></td> </tr>

<tr> <td colspan="2">--apiserver-bind-port int32&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Default: 6443</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If the node should host a new control plane instance, the port for the API Server to bind to.</p></td> </tr>

<tr> <td colspan="2">--certificate-key string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Use this key to decrypt the certificate secrets uploaded by init. The certificate key is a hex encoded string that is an AES key of size 32 bytes.</p></td> </tr>

<tr> <td colspan="2">--config string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a kubeadm configuration file.</p></td> </tr>

<tr> <td colspan="2">--control-plane</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Create a new control plane instance on this node</p></td> </tr>

<tr> <td colspan="2">--discovery-file string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For file-based discovery, a file or URL from which to load cluster information.</p></td> </tr>

<tr> <td colspan="2">--discovery-token string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For token-based discovery, the token used to validate cluster information fetched from the API server.</p></td> </tr>

<tr> <td colspan="2">--discovery-token-ca-cert-hash strings</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For token-based discovery, validate that the root CA public key matches this hash (format: &quot;&lt;type&gt;:&lt;value&gt;&quot;).</p></td> </tr>

<tr> <td colspan="2">--discovery-token-unsafe-skip-ca-verification</td> </tr> <tr> <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">--dry-run</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Don't apply any changes; just output what would be done.</p></td> </tr>

<tr> <td colspan="2">-h, --help</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>help for all</p></td> </tr>

<tr> <td colspan="2">--node-name string</td> </tr> <tr> <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 &quot;target[suffix][+patchtype].extension&quot;. For example, &quot;kube-apiserver0+merge.yaml&quot; or just &quot;etcd.json&quot;. &quot;target&quot; can be one of &quot;kube-apiserver&quot;, &quot;kube-controller-manager&quot;, &quot;kube-scheduler&quot;, &quot;etcd&quot;, &quot;kubeletconfiguration&quot;, &quot;corednsdeployment&quot;. &quot;patchtype&quot; can be one of &quot;strategic&quot;, &quot;merge&quot; or &quot;json&quot; and they match the patch formats supported by kubectl. The default &quot;patchtype&quot; is &quot;strategic&quot;. &quot;extension&quot; must be either &quot;json&quot; or &quot;yaml&quot;. &quot;suffix&quot; is an optional string that can be used to determine which patches are applied first alpha-numerically.</p></td> </tr> …(trimmed)