1KUBERNETES(1)                      Jan 2015                      KUBERNETES(1)
2
3
4

NAME

6       kubeadm token - Manage bootstrap tokens
7
8
9

SYNOPSIS

11       kubeadm token [OPTIONS]
12
13
14

DESCRIPTION

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

OPTIONS

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

OPTIONS INHERITED FROM PARENT COMMANDS

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

SEE ALSO

78       kubeadm(1), kubeadm-token-create(1), kubeadm-token-delete(1),
79       kubeadm-token-generate(1), kubeadm-token-list(1),
80
81
82

HISTORY

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