KUBERNETES(1)(kubernetes)
π KUBERNETES(1)(kubernetes) β bestie edition π
okay so you opened the manual for kubeadm upgrade apply phase addon coredns and honestly? good taste. this is section 1 of the kubernetes manuals, and we're gonna get you fluent, fr fr. π¦
β¨ NAME β¨
kubeadm upgrade apply phase addon coredns β Upgrade the CoreDNS addon π
πΈ SYNOPSIS πΈ
kubeadm upgrade apply phase addon coredns [OPTIONS]
like, that's the whole summoning ritual. options go at the end, bestie. π
π¦ DESCRIPTION π¦
Upgrade the CoreDNS addon. that's it. that's the job. it walks in, it upgrades CoreDNS, it leaves. main character energy, no notes. π
β¨ OPTIONS β¨
--config=""β the path to a kubeadm configuration file. point it at your config and it'll read it. π--dry-run=falseβ do not change any state, just print out what actions would be performed. it's giving window shopping. π defaults tofalse, so if you actually want the preview you gotta turn it on.--kubeconfig="/etc/kubernetes/admin.conf"β the kubeconfig file to use when talking to the cluster. and if the flag is not set, a set of standard locations can be searched for an existing kubeconfig file. so it's not gonna be lost, it'll go looking. π§--patches=""β the path to a directory that contains files named"target[suffix][+patchtype].extension". okay this one is a whole little language so let's break it down:- 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 bykubectl. 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.
- for example,
bestie please read that naming scheme twice before you name a file. the filename is the config. no cap. π
π 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. yes, that's a big deal. π--version=falseβ--version,--version=rawprints version information and quits;--version=vX.Y.Z...sets the reported version. so it can tell you the version or pretend to be one. iconic. π
π 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! π«Ά
and that's the whole page, bestie. every flag, every path, every default, every file-naming rule β nothing skipped, nothing invented. π
πΈ this was Manuals / User for KUBERNETES(1)(kubernetes), dated back in January 2015 with Eric Paris on the byline. slay, go upgrade that CoreDNS. β¨ππ¦
π¦ 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