KUBERNETES(1)(kubernetes)

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

πŸ’– KUBERNETES(1)(kubernetes) πŸ’–

okay bestie, welcome to the kubernetes manual page, section 1 β€” and this particular page is the kubeadm upgrade plan glow-up guide. written up by Eric Paris back in Jan 2015, and she's still serving. let's get into it ✨


✨ NAME ✨

kubeadm upgrade plan β€” check which versions are available to upgrade to, and validate whether your current cluster is upgradeable. no cap, that's the whole job πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

kubeadm upgrade plan [OPTIONS]

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea, bestie: this command checks which versions are available for you to upgrade to, and validates whether your current cluster is even upgradeable in the first place. vibe check before the glow-up, yk? πŸ’…

big caveat incoming: this command can only run on the control plane nodes, and only where the kubeconfig file admin.conf exists. so if you're trying to run this from your little laptop, she's not gonna answer. πŸ™ˆ

and if you wanna skip the internet check? just pass in the optional [version] parameter. boom, offline mode, main character energy ⭐


🌸 OPTIONS 🌸

  • --allow-experimental-upgrades=false β€” shows unstable versions of Kubernetes as an upgrade alternative, and lets you actually upgrade to alpha/beta/release candidate versions of Kubernetes. living dangerously, love that for you πŸ”₯
  • --allow-missing-template-keys=true β€” if true, ignore any errors in templates when a field or map key is missing from the template. heads up: this only applies to golang and jsonpath output formats πŸ’œ
  • --allow-release-candidate-upgrades=false β€” shows release candidate versions of Kubernetes as an upgrade alternative, and allows upgrading to a release candidate version of Kubernetes. slightly less chaotic than experimental, still spicy 🌢️
  • --config="" β€” path to a kubeadm configuration file.
  • --etcd-upgrade=true β€” perform the upgrade of etcd. yes queen, etcd gets the treatment too 🫢
  • --ignore-preflight-errors=[] β€” a list of checks whose errors will be shown as warnings instead of stopping you. example: 'IsPrivilegedUser,Swap'. the value 'all' ignores errors from all checks. (use responsibly, bestie, that's a lot of power 😭)
  • --kubeconfig="/etc/kubernetes/admin.conf" β€” the kubeconfig file to use when talking to the cluster. if the flag isn't set, a set of standard locations can be searched for an existing kubeconfig file 🧚
  • -o, --output="text" β€” output format. one of: text|json|yaml|kyaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file. pick your fighter πŸ’…
  • --print-config=false β€” specifies whether the configuration file that will be used in the upgrade should be printed or not. printing it? slay. not printing it? also slay.
  • --show-managed-fields=false β€” if true, keep the managedFields when printing objects in JSON or YAML format. iykyk ✨

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these ones came from the parent command, so they're like... the family hand-me-downs but make it iconic πŸ’–

  • --rootfs="" β€” the path to the 'real' host root filesystem. this will cause kubeadm to chroot into the provided path. yes, chroot. stay seated πŸ«–
  • --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! (bestie said "i hope a robot does this now" and honestly? same πŸ’€)


and that's the whole page, babes 🫢 this little number lives in the Manuals / User corner of the KUBERNETES(1)(kubernetes) manual, dated back to that January 2015 era. go forth and upgrade responsibly, queen πŸ‘‘πŸ’–

πŸ“¦ where this page comes from