KUBERNETES(1)(kubernetes)

✨ KUBERNETES(1)(kubernetes) ✨

okay bestie, buckle up 💖 this is a page from the kubernetes manual (section 1, the "User" commands section, obviously), and the original author credit goes to Eric Paris, way back in Jan 2015. We'll get to the cute little sign-off at the bottom, don't worry 🎀

---

🌸 NAME 🌸

kubeadm join phase control-plane-prepare all — Prepare the machine for serving a control plane

---

🦋 SYNOPSIS 🦋

kubeadm join phase control-plane-prepare all [OPTIONS]

---

💅 DESCRIPTION 💅

So basically? You're prepping this machine to serve a control plane. That's it. That's the whole vibe. Prepare the machine for serving a control plane ✨

---

👑 OPTIONS 👑

• --apiserver-advertise-address="" — if this node is gonna host a brand new control plane instance, this is the IP address the API Server will advertise that it's listening on. If you don't set it, the default network interface gets used instead, no biggie.
• --apiserver-bind-port=6443 — same situation, node hosting a new control plane instance? This is the port the API Server binds to. Default 6443, iconic.
• --certificate-key="" — use this key to decrypt the certificate secrets that init uploaded. Heads up: the certificate key is a hex encoded string that's an AES key of size 32 bytes 🔐
• --config="" — path to a kubeadm configuration file. Simple as that.
• --control-plane=false — create a new control plane instance on this node. Default is false.
• --discovery-file="" — for file-based discovery, a file or URL to load cluster information from.
• --discovery-token="" — for token-based discovery, the token used to validate the cluster information it fetched from the API server.
• --discovery-token-ca-cert-hash=[] — for token-based discovery, validate that the root CA public key matches this hash. The format is ":". Yes, literally just a colon in the docs, we don't make the rules 💀
• --discovery-token-unsafe-skip-ca-verification=false — for token-based discovery, this lets you join without --discovery-token-ca-cert-hash pinning. It's right there in the name bestie, it says unsafe 🚨
• --dry-run=false — don't apply any changes, just output what would be done. A little look-see, a little window shopping 🛍️
• --node-name="" — specify the node name.
• --patches="" — path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment", "kubeproxydaemonset". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically. 📝
• --tls-bootstrap-token="" — specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
• --token="" — use this token for both discovery-token and tls-bootstrap-token when those values aren't provided. Two-for-one deal, we love efficiency 🫶

---

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

• --rootfs="" — the path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version.

---

🌈 SEE ALSO 🌈

• kubeadm-join-phase-control-plane-prepare(1),

---

⭐ 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! 😭 (the "hopefully" is doing so much heavy lifting there fr fr)

---

and that's the whole page, bestie 💜 this came out of the Manuals source, User section, filed under KUBERNETES(1)(kubernetes), dated back to Jan 2015 with Eric Paris on the byline. slay, go prep that control plane 🎀✨