KUBERNETES(1)(kubernetes)

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

✨ KUBERNETES(1)(kubernetes) ✨

okay bestie, pull up a chair πŸ’– this is a kubernetes manual page, section 1, and it's literally all about one very specific little command that does one very specific little thing. no cap.


πŸŽ€ NAME πŸŽ€

kubeadm upgrade node phase addon all β€” Upgrade all the addons

🌸 SYNOPSIS 🌸

kubeadm upgrade node phase addon all [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

Upgrade all the addons

that's it. that's the whole description. the manpage said what it said and honestly? iconic brevity. slay. πŸ’…


✨ OPTIONS ✨

  • --config="" β€” Path to a kubeadm configuration file.
  • --dry-run=false β€” Do not change any state, just output the actions that would be performed. the "look but don't touch" mode, fr fr πŸ‘€
  • --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 say anything, it goes hunting on its own 🧚
  • --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 so the --patches naming scheme is a whole little grammar β€” target, optional suffix, optional patchtype, extension. get the order wrong and it's giving nothing. read it twice. iykyk πŸ’€

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS πŸ’œ

these ones came from the parent command, so they're not even this command's own. nepotism? maybe. useful? absolutely. 🫢

  • --rootfs="" β€” The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. yes, chroot. it's doing a whole transformation sequence ✨
  • --version=false β€” --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version.

🌈 SEE ALSO 🌈

(that trailing comma is doing its own thing and we respect it πŸ‘‘)


πŸ“ 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!

ngl that last part is such a mood β€” "we wrote this by hand once and we're praying the robots took over." and honestly, they probably did πŸ™ˆ


🌟 cute sign-off: this page lives in the Manuals manual, User section, and the version stamp on the bottom is KUBERNETES(1)(kubernetes), dated Jan 2015. go forth and upgrade those addons, bestie β€” you got this πŸ’–βœ¨πŸŽ€
πŸ“¦ where this page comes from