KUBERNETES(1)(kubernetes)

✨ KUBERNETES(1)(kubernetes) — the kubeadm join phase control-plane-prepare control-plane glow-up ✨

okay bestie, so this is a page from the kubernetes manual set, section 1, and it's the whole vibe of getting a fresh control plane node's manifests born into the world. It was originally compiled by Eric Paris back in Jan 2015, and it's been living in the manual since. 💖

---

🌸 NAME 🌸

kubeadm join phase control-plane-prepare control-plane — Generate the manifests for the new control plane components

---

🦋 SYNOPSIS 🦋

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

---

💅 DESCRIPTION 💅

Generate the manifests for the new control plane components

like. that's the whole job. it generates the manifests for your new control plane components and it does it well. main character energy fr. 👑

---

✨ OPTIONS ✨

• --apiserver-advertise-address="" — If this node is gonna host a new control plane instance, this is the IP address the API Server will advertise it's listening on. If you don't set it, the default network interface gets used. no cap.
• --apiserver-bind-port=6443 — If this node is hosting a new control plane instance, this is the port the API Server binds to. 6443 is the default, as ever. 🎀
• --config="" — Path to a kubeadm configuration file. drop the path, let it cook.
• --control-plane=false — Create a new control plane instance on this node. default is false, so you gotta actually ask for it bestie.
• --dry-run=false — Don't apply any changes; just output what would be done. window shopping, but for cluster changes. 🙈
• --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.

---

🫶 OPTIONS INHERITED FROM PARENT COMMANDS 🫶

• --rootfs="" — The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. it's giving "go live inside this directory actually".
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version. yes it both prints and sets, depending on what you feed it. iconic behavior. ✨

---

🌈 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!

---

⚠️ heads up bestie: --dry-run=false is the default, so unless you flip it, this command is gonna actually do the thing. no take-backs, no undo button, periodt. 💀

---

and that's the whole page, from the Manuals / User corner of the KUBERNETES(1)(kubernetes) section, dated back to that January 2015 energy. stay slay, go generate those manifests. 🦋✨💖