kubeadm_token_create [page]deterministic
Create bootstrap tokens on the server
### Synopsis
This command will create a bootstrap token for you. You can specify the usages for this token, the "time to live" and an optional human friendly description.
The [token] is the actual token to write. This should be a securely generated random token of the form "[a-z0-9]{6}.[a-z0-9]{16}". If no [token] is given, kubeadm will generate a random token instead.
``` kubeadm token create [token] ```
### Options
<table style="width: 100%; table-layout: fixed;"> <colgroup> <col span="1" style="width: 10px;" /> <col span="1" /> </colgroup> <tbody>
<tr> <td colspan="2">--certificate-key string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>When used together with '--print-join-command', print the full 'kubeadm join' flag needed to join the cluster as a control-plane. To create a new certificate key you must use 'kubeadm init phase upload-certs --upload-certs'.</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">--description string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>A human friendly description of how this token is used.</p></td> </tr>
<tr> <td colspan="2">--groups strings Default: "system:bootstrappers:kubeadm:default-node-token"</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Extra groups that this token will authenticate as when used for authentication. Must match "\Asystem:bootstrappers:[a-z0-9:-]{0,255}[a-z0-9]\z"</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 create</p></td> </tr>
<tr> <td colspan="2">--print-join-command</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Instead of printing only the token, print the full 'kubeadm join' flag needed to join the cluster using the token.</p></td> </tr>
<tr> <td colspan="2">--ttl duration Default: 24h0m0s</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The duration before the token is automatically deleted (e.g. 1s, 2m, 3h). If set to '0', the token will never expire</p></td> </tr>
<tr> <td colspan="2">--usages strings Default: "signing,authentication"</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Describes the ways in which this token can be used. You can pass --usages multiple times or provide a comma separated list of options. Valid options: [signing,authentication]</p></td> </tr>
</tbody> </table>
### Options inherited from parent commands
<table style="width: 100%; table-layout: fixed;"> <colgroup> <col span="1" style="width: 10px;" /> <col span="1" /> </colgroup> <tbody>
<tr> <td colspan="2">--dry-run</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Whether to enable dry-run mode or not</p></td> </tr>
<tr> <td colspan="2">--kubeconfig string Default: "/etc/kubernetes/admin.conf"</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file.</p></td> </tr>
<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>