kubeadm_join_phase_kubelet-wait-bootstrap [page]deterministic

reference

### Synopsis

Wait for the kubelet to bootstrap itself

``` kubeadm join phase kubelet-wait-bootstrap [flags] ```

### Options

<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">--cri-socket string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</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 kubelet-wait-bootstrap</p></td> </tr>

</tbody> </table>

### Options inherited from parent commands

<tr> <td colspan="2">--rootfs string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.</p></td> </tr>

</tbody> </table>

Sources

reference/setup-tools/kubeadm/generated/kubeadm_join/kubeadm_join_phase_kubelet-wait-bootstrap.md · doc — “kubeadm_join_phase_kubelet-wait-bootstrap”

Related (3)

part_of Synopsis — describes conf=1

part_of Options — describes conf=1

part_of Options inherited from parent commands — describes conf=1

← all Docs