KUBERNETES(1)(kubernetes)
β¨ KUBERNETES(1)(kubernetes) β the kubeadm init phase addon coredns glow-up β¨
okay bestie, listen. this is a page from the kubernetes manual, and ngl it's kind of a niche little corner of it, but it's so important and we're gonna get through it together. no cap. π
πΈ NAME πΈ
kubeadm init phase addon coredns β install the CoreDNS addon to a Kubernetes cluster π
π¦ SYNOPSIS π¦
kubeadm init phase addon coredns [OPTIONS]
π DESCRIPTION π
so what this does is: it installs the CoreDNS addon components via the API server. that's it, that's the job, and it ate. β¨
β οΈ but bestie, read this part twice: even though the DNS server is deployed, it will not be scheduled until CNI is installed. like, it's there, it's just sitting pretty waiting for its moment. it's giving main character waiting for her entrance. π
π OPTIONS π
--config=""β path to a kubeadm configuration file. that's it, that's the vibe. π--dry-run=falseβ don't apply any changes, just output what would be done. so you can peek without committing, we love a low-stakes preview. π--feature-gates=""β a set ofkey=valuepairs that describe feature gates for various features. the options are:RootlessControlPlane=true|false(ALPHA β default=false). yes it's alpha, yes it's off by default, treat it accordingly. π₯--image-repository="registry.k8s.io"β choose a container registry to pull control plane images from. default isregistry.k8s.io, periodt.--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. π--kubernetes-version="stable-1"β choose a specific Kubernetes version for the control plane.--print-manifest=falseβ print the addon manifests toSTDOUTinstead of installing them. manifests but make it β¨just for youβ¨.--service-cidr="10.96.0.0/12"β use an alternative range of IP address for service VIPs.--service-dns-domain="cluster.local"β use an alternative domain for services, e.g."myorg.internal". π
π§ OPTIONS INHERITED FROM PARENT COMMANDS π§
these ones came from the parent command, so they're like the family hand-me-downs but make them iconic:
--rootfs=""β the path to the'real'host root filesystem. this will cause kubeadm tochrootinto the provided path. π yes, chroot. be normal about it.--version=falseβ--version,--version=rawprints version information and quits;--version=vX.Y.Z...sets the reported version.
π 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. π«Ά this one's from the kubernetes manual (section 1, user commands), and the footer says it all: manuals, user, KUBERNETES(1)(kubernetes). mwah. π
β¨ππ¦πΈ
π¦ 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