KUBERNETES(1)(kubernetes)

💖 KUBERNETES(1)(kubernetes) — the kubeadm token create era 💖

okay bestie, welcome to the kubernetes manual section (that's the manual name, keep up 🫶), and today's main character is kubeadm token create. Originally written down by Eric Paris back in January 2015 — yeah, a whole elder, we stan a pioneer 🎀

---

✨ NAME ✨

kubeadm token create — bestie, we're making bootstrap tokens on the server. that's it, that's the job 💅

---

✨ SYNOPSIS ✨

kubeadm token create [OPTIONS]

---

✨ DESCRIPTION ✨

okay so this command literally just creates a bootstrap token for you. you get to choose the usages for that token, the "time to live", and optionally a lil human friendly description, because tokens deserve lore too 🌸

the [token] is the actual token being written. and no cap, it needs to be a securely generated random token shaped exactly like this:

[a-z0-9]{6}.[a-z0-9]{16}

if you don't hand over a [token], don't even stress — kubeadm will generate a random one for you instead. iconic behaviour, honestly 👑

---

✨ OPTIONS ✨

• --certificate-key="" — when you use this alongside '--print-join-command', it prints the full 'kubeadm join' flag you need to join the cluster as a control-plane. and listen, if you wanna create a brand new certificate key you must use 'kubeadm init phase upload-certs --upload-certs'. no shortcuts, bestie 🦋
• --config="" — path to a kubeadm configuration file. give it the file, it does the thing 💜
• --description="" — a human friendly description of how this token is used. cute, explanatory, we love ✨
• --groups=[system:bootstrappers:kubeadm:default-node-token] — extra groups this token will authenticate as when it's used for authentication. and it must match this regex exactly:

\Asystem:bootstrappers:[a-z0-9:-]{0,255}[a-z0-9]\z

yes it's giving strict, that's the point 🙈

• --print-join-command=false — instead of printing just the token, print the full 'kubeadm join' flag needed to join the cluster using that token 🔥
• --ttl=24h0m0s — the duration before the token is automatically deleted (like 1s, 2m, 3h). and if you set it to '0', the token will never expire — immortal token energy, use responsibly 💀
• --usages=[signing,authentication] — describes the ways this token can be used. you can pass --usages multiple times or just hand over a comma separated list of options. valid options: [signing,authentication] 🎀

---

✨ OPTIONS INHERITED FROM PARENT COMMANDS ✨

these come down from the parent command, they're the family heirlooms 💖

• --dry-run=false — whether to enable dry-run mode or not. peek, don't commit, we love a cautious queen 🌈
• --kubeconfig="/etc/kubernetes/admin.conf" — the kubeconfig file to use when talking to the cluster. if the flag isn't set, a set of standard locations can be searched for an existing kubeconfig file 🧚
• --rootfs="" — the path to the 'real' host root filesystem. this will cause kubeadm to chroot into the provided path. lowkey powerful, highkey real 🫶
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version ⭐

---

✨ SEE ALSO ✨

kubeadm-token(1),

go read that one too bestie, it's the sibling, the duo, the it-girl pairing 👑

---

✨ HISTORY ✨

January 2015, originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since! 😭 (we're praying for the automation, fr fr)

---

and that's the whole vibe check — this manual page lives under Manuals, in the User section, for KUBERNETES(1)(kubernetes), and the header's date energy is that very same Jan 2015 moment. mwah, bye bestie 💅✨💖