KUBERNETES(1)(kubernetes)
β¨ KUBERNETES(1)(kubernetes) β¨
okay bestie, welcome to the kubernetes corner of the manual pages, section 1, and today's main character is a lil subcommand that has one very specific job. buckle up, it's giving sysadmin β¨
π NAME π
kubeadm upgrade node phase control-plane β upgrade the control plane instance deployed on this node, if any π«Ά
πΈ SYNOPSIS πΈ
kubeadm upgrade node phase control-plane [OPTIONS]
π¦ DESCRIPTION π¦
Upgrade the control plane instance deployed on this node, if any.
that's it. that's the whole vibe. if there's a control plane chilling on this node, it's getting upgraded. if there isn't one? then, like, nothing happens, no cap π
π OPTIONS π
--certificate-renewal=trueβ do the whole certificate renewal thing for the certs that get used by components changed during upgrades. yes queen, fresh certs π--config=""β the path to a kubeadm configuration file.--dry-run=falseβ don't actually change any state, just print out the actions that would have happened. it's giving dress rehearsal π©°--etcd-upgrade=trueβ go ahead and upgrade etcd.--kubeconfig="/etc/kubernetes/admin.conf"β the kubeconfig file to use when talking to the cluster. if this flag isn't set, a bunch of standard locations get searched for an existing kubeconfig file, so it'll lowkey go looking for you π--patches=""β path to a directory full of files named"target[suffix][+patchtype].extension". for example,"kube-apiserver0+merge.yaml"or just"etcd.json". so"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 those match the patch formats supported by kubectl. the default"patchtype"is"strategic"."extension"has to be either"json"or"yaml". and"suffix"is an optional string you can use to figure out which patches get applied first, alpha-numerically. obsessed with this naming scheme tbh β¨
π OPTIONS INHERITED FROM PARENT COMMANDS π
--rootfs=""β the path to the 'real' host root filesystem. this makes kubeadm chroot into the path you gave it. it's literally moving in π--version=falseβ--version,--version=rawprints version information and quits;--version=vX.Y.Z...sets the reported version.
π 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! π iconic honestly
and that's the whole page bestie β brought to you by the Manuals girlies on User, for KUBERNETES(1)(kubernetes), dated all the way back in January 2015. slay, stay upgraded, and don't forget to renew those certs πβ¨
π¦ 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