KUBERNETES(1)(kubernetes)

👑 KUBERNETES(1)(kubernetes) — kubeadm upgrade node phase kubelet-config 💅

okay bestie, sit down, hydrate, because we're doing cluster surgery and it's honestly giving main character energy. this is a page from the kubernetes manual, section 1, and it's all about one very specific little glow-up for one very specific node. 🦋

---

✨ NAME ✨

kubeadm upgrade node phase kubelet-config — Upgrade the kubelet configuration for this node

---

🌸 SYNOPSIS 🌸

kubeadm upgrade node phase kubelet-config [OPTIONS]

---

💖 DESCRIPTION 💖

so here's the vibe: this command upgrades the kubelet configuration for this node — and the way it does it is by downloading that config straight from the kubelet-config ConfigMap that lives in your cluster. no cap. it literally just goes and fetches it. 💅

---

🎀 OPTIONS 🎀

• --config="" — path to a kubeadm configuration file. that's it, that's the whole thing. 🍓
• --dry-run=false — do not change any state, just output the actions that would be performed. a little look-but-don't-touch moment, we love a preview. 🙈
• --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. she'll go looking, she's resourceful. 🔥
• --patches="" — path to a directory that contains files named target[suffix][+patchtype].extension. for example, kube-apiserver0+merge.yaml or just etcd.json. okay so let's break down this naming scheme because it's a whole little language, iykyk:
  • 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.

so yes, the ordering is alphabetical-ish, and yes, that matters. ⭐

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

• --rootfs="" — the path to the 'real' host root filesystem. this will cause kubeadm to chroot into the provided path. she's going in. 🧚
• --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version. three moods, one flag. 💜

---

🫶 SEE ALSO 🫶

• kubeadm-upgrade-node-phase(1),

---

📜 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! 😭 the way that last clause is so real.

---

and that's the whole page, bestie — no notes, periodt. this cutie came out of the kubernetes manual, section 1, under Manuals / User, and the original was dated way back in Jan 2015 (yeah, ancient, iconic, historic). go forth and configure that kubelet. 💖✨🎀