KUBERNETES(1)(kubernetes)
β¨ 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 tofalse.--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=rawprints 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
- arch rolling: kubeadm 1.37.2-1 Β· Apache-2.0
- fedora 43: kubernetes1.37-kubeadm 1.37.0-3.fc43
- fedora 43: kubernetes1.37-kubeadm 1.37.1-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSD-3-Clause-HP AND CC-BY-4.0 AND ISC AND MIT AND MPL-2.0
- fedora 44: kubernetes1.37-kubeadm 1.37.0-3.fc44
- fedora 44: kubernetes1.37-kubeadm 1.37.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND BSD-3-Clause-HP AND CC-BY-4.0 AND ISC AND MIT AND MPL-2.0
- nixpkgs unstable: kubernetes 1.37.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms