KUBERNETES(1)(kubernetes)

πŸ“¦
version 1.37.2 Β· 5 versions
, in arch rolling, fedora 43, fedora 44, nixpkgs unstable

✨ 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=raw prints 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