KUBERNETES(1)(kubernetes)

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

✨ KUBERNETES(1)(kubernetes) β€” the kubeadm edition ✨

okay bestie, sit down, hydrate, and let's talk about kubeadm upgrade apply phase kubelet-config πŸ’… this is one of those little hidden gems that lives under kubeadm upgrade apply phase, and it's giving very specific, very useful energy 🫢


πŸŽ€ NAME πŸŽ€

kubeadm upgrade apply phase kubelet-config β€” lowkey just here to Upgrade the kubelet configuration for this node ✨


🌸 SYNOPSIS 🌸

kubeadm upgrade apply phase kubelet-config [OPTIONS]

πŸ¦‹ DESCRIPTION πŸ¦‹

So what does it actually do, you ask? It upgrades the kubelet configuration for this node β€” and the way it gets that config is by downloading it from the kubelet-config ConfigMap that's chilling in your cluster ☁️ no cap, that's the whole vibe. Pull the config from the cluster, apply it to the node, move on with your day πŸ’–


πŸ’… OPTIONS πŸ’…

  • --config="" β€” path to a kubeadm configuration file. it's empty by default, so nothing's set unless you say so πŸ™ˆ
  • --dry-run=false β€” do not change any state, just print out what actions would be performed πŸ‘€ perfect for when you want the tea without the consequences. defaults to false.
  • --kubeconfig="/etc/kubernetes/admin.conf" β€” the kubeconfig file to use when talking to the cluster πŸ’¬ if you don't set this flag, a set of standard locations gets searched for an existing kubeconfig file. so it'll go looking for one like a bestie looking for you in a crowd 🫢
  • --patches="" β€” path to a directory that contains files named "target[suffix][+patchtype].extension" 🧚 for example, "kube-apiserver0+merge.yaml" or just "etcd.json". here's the breakdown, because this one has lore:
    • "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 these match the patch formats supported by kubectl. the default "patchtype" is "strategic" ✨
    • "extension" must be either "json" or "yaml" β€” no third option, periodt πŸ“
    • "suffix" is an optional string that can be used to determine which patches are applied first, alpha-numerically πŸ”€

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

  • --rootfs="" β€” the path to the 'real' host root filesystem 🏠 this will cause kubeadm to chroot into the provided path. yes, chroot. it's giving commitment.
  • --version=false β€” --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version πŸ”’ so you can either ask the version or tell it what to be. main character energy fr fr.

πŸ”₯ 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 πŸŽ€ this was rendered from the KUBERNETES(1)(kubernetes) manual, Manuals / User section, with source and date living their best life as January 2015, Eric Paris πŸ’– go forth, upgrade that kubelet config, and slay βœ¨πŸ«ΆπŸ’…

πŸ“¦ where this page comes from