KUBERNETES(1)(kubernetes)

💖 KUBERNETES(1)(kubernetes) 💖

okay bestie, welcome to the kubernetes manual, section 1 — and today's main character is a lil command called kubeadm init phase control-plane apiserver. yes it's a mouthful, no we're not shortening it, it's iconic like that. 🫶

---

✨ NAME ✨

kubeadm init phase control-plane apiserver — she generates the kube-apiserver static Pod manifest. that's it, that's her whole job, and she ate. 💅

---

✨ SYNOPSIS ✨

kubeadm init phase control-plane apiserver [OPTIONS]

---

✨ DESCRIPTION ✨

Generates the kube-apiserver static Pod manifest. literally just that. one job, done flawlessly, no notes. 👑

---

✨ OPTIONS ✨

okay this is the part where we go through every single flag, no skipping, because we do NOT leave details behind in this house. 🌸

• --apiserver-advertise-address="" — the IP address the API Server will advertise it's listening on. if you don't set it, the default network interface gets used instead. lowkey convenient.
• --apiserver-bind-port=6443 — the port for the API Server to bind to. default 6443, iconic number.
• --apiserver-extra-args= — a set of extra flags to pass to the API Server, or to override default ones, in form of =. go off, customize.
• --cert-dir="/etc/kubernetes/pki" — the path where to save and store the certificates. default is /etc/kubernetes/pki, keep those certs cozy. 🎀
• --config="" — path to a kubeadm configuration file.
• --control-plane-endpoint="" — specify a stable IP address or DNS name for the control plane.
• --dry-run=false — don't apply any changes; just output what would be done. bestie behavior honestly, look before you leap. 🙈
• --feature-gates="" — a set of key=value pairs that describe feature gates for various features. options are: RootlessControlPlane=true|false (ALPHA - default=false). it's giving experimental energy, be careful out there. ⚠️
• --image-repository="registry.k8s.io" — choose a container registry to pull control plane images from. default is registry.k8s.io.
• --kubernetes-version="stable-1" — choose a specific Kubernetes version for the control plane. default stable-1.
• --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. yes that's a lot of rules, she's complex like that. 💅
• --service-cidr="10.96.0.0/12" — use alternative range of IP address for service VIPs. default 10.96.0.0/12.

---

✨ OPTIONS INHERITED FROM PARENT COMMANDS ✨

these ones come from the parent command, so they're like... family flags. they show up to every party. 🦋

• --rootfs="" — the path to the 'real' host root filesystem. this will cause kubeadm to chroot into the provided path. (that's real with the quotes, she said what she said.)
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version. three modes, one flag, versatility queen. ✨

---

✨ SEE ALSO ✨

go read her sister page, they're a matching set:

• kubeadm-init-phase-control-plane(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 way this manpage has been out here since 2015 and still didn't get auto-generated... anyway, we respect the origin story. 🫶

---

and that's the whole page bestie — this one lives in the Manuals pile, User section, KUBERNETES(1)(kubernetes), dated Jan 2015. now go generate that apiserver manifest, you absolute legend. 💖✨🎀