KUBERNETES(1)(kubernetes)
π KUBERNETES(1)(kubernetes) π
okay bestie, sit down, hydrate, and let me tell you about this lil gem from the kubernetes manual. we're in the kubeadm cinematic universe today and it's lowkey iconic.
β¨ NAME β¨
kubeadm init phase etcd local β generate the static Pod manifest file for a local, single-node local etcd instance. that's it, that's the whole job, and she does it flawlessly π
π¦ SYNOPSIS π¦
kubeadm init phase etcd local [OPTIONS]
πΈ DESCRIPTION πΈ
okay so what this actually does: it generates the static Pod manifest file for a local, single-node local etcd instance. one etcd, one node, one manifest, no drama, no cap. the way she just makes the file for you?? obsessed π
π OPTIONS π
--cert-dir="/etc/kubernetes/pki" β the path where to save and store the certificates. she needs a home for her certs, give her one π--config="" β path to a kubeadm configuration file. default is empty, meaning "nah, no config file, we're going off vibes and flags"--dry-run=false β don't apply any changes; just output what would be done. the manifestation option fr fr, you get to see the future without touching anything β¨--image-repository="registry.k8s.io" β choose a container registry to pull control plane images from--patches="" β path to a directory that contains files named"target[suffix][+patchtype].extension". for example,"kube-apiserver0+merge.yaml"or just"etcd.json".
okay this one is a whole syllabus so let me break it down the way a study group would π§
"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 bykubectl. 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 causekubeadmtochrootinto the provided path. she's going undercover into the host filesystem, main character energy honestly--version=false β--version,--version=rawprints version information and quits;--version=vX.Y.Z...sets the reported version
π₯ EXAMPLE π₯
# Generates the static Pod manifest file for etcd, functionally
# equivalent to what is generated by kubeadm init.
kubeadm init phase etcd local
# Generates the static Pod manifest file for etcd using options
# read from a configuration file.
kubeadm init phase etcd local --config config.yaml
π SEE ALSO π
π 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! iykyk π
and that's the whole page bestie, no notes, ate and left no crumbs π this lil writeup lives in the Manuals manual set for User, under KUBERNETES(1)(kubernetes), and the byline energy belongs to Eric Paris, Jan 2015 β so basically this page is a vintage icon, periodt βπ«Ά
π¦ where this page comes from
- arch rolling: kubeadm 1.37.2-1 Β· Apache-2.0
- fedora 43: kubernetes1.37-kubeadm 1.37.0-3.fc43
- fedora 43: kubernetes1.37-kubeadm 1.37.1-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSD-3-Clause-HP AND CC-BY-4.0 AND ISC AND MIT AND MPL-2.0
- fedora 44: kubernetes1.37-kubeadm 1.37.0-3.fc44
- fedora 44: kubernetes1.37-kubeadm 1.37.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSD-3-Clause-HP AND CC-BY-4.0 AND ISC AND MIT AND MPL-2.0
- nixpkgs unstable: kubernetes 1.37.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms