1KUBERNETES(1)(kubernetes)                            KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7

NAME

9       kubeadm token - Manage bootstrap tokens
10
11
12

SYNOPSIS

14       kubeadm token [OPTIONS]
15
16
17

DESCRIPTION

19       This  command  manages bootstrap tokens. It is optional and needed only
20       for advanced use cases.
21
22
23       In short, bootstrap tokens  are  used  for  establishing  bidirectional
24       trust  between  a  client  and a server.  A bootstrap token can be used
25       when a client (for example a node that is about to  join  the  cluster)
26       needs to trust the server it is talking to. Then a bootstrap token with
27       the "signing" usage can be used.  bootstrap tokens can also function as
28       a  way to allow short-lived authentication to the API Server (the token
29       serves as a way for the API Server to trust the  client),  for  example
30       for doing the TLS Bootstrap.
31
32
33       What is a bootstrap token more exactly?
34        -  It  is a Secret in the kube-system namespace of type "bootstrap.ku‐
35       bernetes.io/token".
36        - A bootstrap token must be of  the  form  "[a-z0-9]{6}.[a-z0-9]{16}".
37       The former part is the public token ID,
38          while  the latter is the Token Secret and it must be kept private at
39       all circumstances!
40        - The name of the Secret must be named "bootstrap-token-(token-id)".
41
42
43       You can read more about bootstrap tokens here:
44         https://kubernetes.io/docs/admin/bootstrap-tokens/
45
46
47

OPTIONS

49       --dry-run=false      Whether to enable dry-run mode or not
50
51
52       --kubeconfig="/etc/kubernetes/admin.conf"      The kubeconfig  file  to
53       use when talking to the cluster. If the flag is not set, a set of stan‐
54       dard locations can be searched for an existing kubeconfig file.
55
56
57

OPTIONS INHERITED FROM PARENT COMMANDS

59       --azure-container-registry-config=""      Path to the  file  containing
60       Azure container registry configuration information.
61
62
63       --log-flush-frequency=5s       Maximum  number  of  seconds between log
64       flushes
65
66
67       --rootfs=""      [EXPERIMENTAL]  The  path  to  the  'real'  host  root
68       filesystem.
69
70
71       --version=false      Print version information and quit
72
73
74

SEE ALSO

76       kubeadm(1),      kubeadm-token-create(1),      kubeadm-token-delete(1),
77       kubeadm-token-generate(1), kubeadm-token-list(1),
78
79
80

HISTORY

82       January 2015, Originally compiled by Eric Paris (eparis at  redhat  dot
83       com)  based  on the kubernetes source material, but hopefully they have
84       been automatically generated since!
85
86
87
88Manuals                              User            KUBERNETES(1)(kubernetes)
Impressum