KUBERNETES(1)(kubernetes)

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

πŸ‘‘ KUBERNETES(1) β€” the kubernetes manual, bestie edition

okay so hi!! you're looking at the kubernetes manual page (section 1, the user commands one πŸ’…). this particular page is all about one very specific little command, and honestly? she's niche but she's important. let's get into it 🫢


✨ NAME ✨

kubeadm upgrade apply phase control-plane β€” literally just: Upgrade the control plane. that's the whole vibe. that's what she does. πŸŽ€


🌸 SYNOPSIS 🌸

kubeadm upgrade apply phase control-plane [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

Upgrade the control plane.

that's it. that's the description. short, sweet, main character energy, no notes. ✨


πŸ’– OPTIONS πŸ’–

okay this is the part where it gets juicy. every single flag, no skipping, i promised:

  • --certificate-renewal=true β€” Perform the renewal of certificates used by component changed during upgrades. so if a component got swapped out mid-upgrade, its certs get a lil glow-up too πŸ”„
  • --config="" β€” Path to a kubeadm configuration file. point her at your config file and she'll read it, no cap πŸ“„
  • --dry-run=false β€” Do not change any state, just output what actions would be performed. it's giving rehearsal β€” nothing actually happens, she just tells you what she would do πŸ™ˆ
  • --etcd-upgrade=true β€” Perform the upgrade of etcd. yes queen, upgrade the etcd too πŸ”₯
  • --kubeconfig="/etc/kubernetes/admin.conf" β€” The kubeconfig file to use when talking to the cluster. If the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. so if you don't set it, she goes hunting in the usual spots πŸ•΅οΈβ™€οΈ
  • --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. β€” okay this one is a whole meal, read it twice, iykyk πŸ“

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these came from the parent command, she's just borrowing them fr fr:

  • --rootfs="" β€” The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. yes bestie she will literally chroot into it πŸ‘€
  • --version=false β€” --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version. so you can ask her her version, or tell her what version to pretend to be πŸ’€

⭐ SEE ALSO ⭐

go read that one next, she's the friend-of-a-friend 🧚


πŸ’œ 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!

like, respect to Eric, but the manpage itself is hoping it got autogenerated at some point and honestly? same energy 😭


okay that's the whole page!! you ate this. go upgrade that control plane responsibly, bestie πŸ’…βœ¨

this was KUBERNETES(1)(kubernetes) from the Manuals set, User section β€” written up by Eric Paris way back in January 2015 πŸŽ€ mwah, love u, bye!! 🫢🌸

πŸ“¦ where this page comes from