KUBERNETES(1)(kubernetes)

📦
version 1.37.2 · 4 versions
, in arch rolling, fedora 43, fedora 44, nixpkgs unstable

💖 KUBERNETES(1)(kubernetes) 💖

okay bestie, so this is a page from the kubernetes manual (section 1, "kubernetes"), and it's all about one lil' subcommand that does one big job. pull up a chair, grab a boba, we're doing this. 🧋✨

🌸 NAME 🌸

kubeadm init phase control-plane controller-manager — generates the kube-controller-manager static Pod manifest. that's it, that's the whole job. it makes the manifest. slay. 💅

✨ SYNOPSIS ✨

kubeadm init phase control-plane controller-manager [OPTIONS]

🦋 DESCRIPTION 🦋

Generates the kube-controller-manager static Pod manifest.

like. it literally just writes out the manifest file for the kube-controller-manager static Pod. no cap. that's the entire vibe of this command. 🎀

👑 OPTIONS 👑

  • --cert-dir="/etc/kubernetes/pki" — the path where to save and store the certificates. yes the default is literally /etc/kubernetes/pki, she lives there, respect her. 💖
  • --config="" — path to a kubeadm configuration file.
  • --controller-manager-extra-args= — a set of extra flags to pass to the Controller Manager or override default ones, in the form of =. yes, in the form of =. that's the whole spec. iykyk. 🙈
  • --dry-run=false — don't apply any changes; just output what would be done. the "i'm just looking, i'm not buying" of flags. set it to true and nothing actually happens, you just get to peek. 👀
  • --image-repository="registry.k8s.io" — choose a container registry to pull control plane images from. default is registry.k8s.io, she's the moment. 🔥
  • --kubernetes-version="stable-1" — choose a specific Kubernetes version for the control plane. default stable-1. iconic.
  • --patches="" — path to a directory that contains files named "target[suffix][+patchtype].extension". 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 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.

ngl this one is a whole entire naming convention and it's giving very specific. read it twice, bestie. 🫶

  • --pod-network-cidr="" — specify range of IP addresses for the pod network. if set, the control plane will automatically allocate CIDRs for every node. 🌈

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

these bad boys come down from the parent command, they're not even this command's own, they just show up like a supportive bestie. 🥹

  • --rootfs="" — the path to the 'real' host root filesystem. this will cause kubeadm to chroot into the provided path. yes it chroots. she's moving in. 💀
  • --version=false — --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version.

⭐ SEE ALSO ⭐

go read that one next, it's the parent, it's the main character, this command is literally its child. 👑

🎀 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. go forth, generate that kube-controller-manager static Pod manifest, and remember: --dry-run=true first, always. 🔥

this lil' page lives in the Manuals section, User subsection, under KUBERNETES(1)(kubernetes), and it's dated Jan 2015. mwah. 💋

📦 where this page comes from