KUBERNETES(1)(kubernetes)

πŸ’– KUBERNETES(1)(kubernetes) πŸ’–

okay so bestie, before we even start β€” this whole page lives in the kubernetes manual, section 1, and it was originally written by Eric Paris back in January 2015 (we'll do a lil shoutout at the bottom, don't worry). now sit down, grab a boba, and let's talk about static Pod manifests 🧚


✨ NAME ✨

kubeadm init phase control-plane all β€” Generate all static Pod manifest files

no cap, that's the whole job description πŸ’…


🌸 SYNOPSIS 🌸

kubeadm init phase control-plane all [OPTIONS]

that's it, that's the shape of it πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

Generate all static Pod manifest files.

like. all of them. every single control plane component, at once, in one go. main character energy fr fr πŸ‘‘


✨ OPTIONS ✨

okay this is the part where you screenshot the page, bestie. every single flag, exactly as it is:

  • --apiserver-advertise-address="" β€” The IP address the API Server will advertise it's listening on. If not set the default network interface will be used.
  • --apiserver-bind-port=6443 β€” Port for the API Server to bind to.
  • --apiserver-extra-args= β€” A set of extra flags to pass to the API Server or override default ones in form of =
  • --cert-dir="/etc/kubernetes/pki" β€” The path where to save and store the certificates.
  • --config="" β€” Path to a kubeadm configuration file.
  • --control-plane-endpoint="" β€” Specify a stable IP address or DNS name for the control plane.
  • --controller-manager-extra-args= β€” A set of extra flags to pass to the Controller Manager or override default ones in form of =
  • --dry-run=false β€” Don't apply any changes; just output what would be done.
  • --feature-gates="" β€” A set of key=value pairs that describe feature gates for various features. Options are: RootlessControlPlane=true|false (ALPHA - default=false)
  • --image-repository="registry.k8s.io" β€” Choose a container registry to pull control plane images from
  • --kubernetes-version="stable-1" β€” Choose a specific Kubernetes version for the control plane.
  • --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.
  • --pod-network-cidr="" β€” Specify range of IP addresses for the pod network. If set, the control plane will automatically allocate CIDRs for every node.
  • --scheduler-extra-args= β€” A set of extra flags to pass to the Scheduler or override default ones in form of =
  • --service-cidr="10.96.0.0/12" β€” Use alternative range of IP address for service VIPs.
the --patches one is long but do not skip it, i swear. the naming scheme is the whole plot πŸ“

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these ones come from the parent, so they're basically the family heirlooms πŸ’œ

  • --rootfs="" β€” The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path.
  • --version=false β€” --version, --version=raw prints version information and quits; --version=vX.Y.Z... sets the reported version

⭐ EXAMPLE ⭐

here's the vibe in action, copy-paste ready:

# Generates all static Pod manifest files for control plane components,
# functionally equivalent to what is generated by kubeadm init.
kubeadm init phase control-plane all

# Generates all static Pod manifest files using options read from a configuration file.
kubeadm init phase control-plane all --config config.yaml

ate. no crumbs. πŸ”₯


🫢 SEE ALSO 🫢

go read that one too, it's the sibling 🧚


πŸ’€ 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 page bestie, you're literally a control-plane manifest generator now πŸ’…βœ¨

Manuals β†’ User β†’ KUBERNETES(1)(kubernetes) β€” compiled way back in January 2015, still iconic, still serving looks πŸ‘‘πŸ’–

πŸ“¦ where this page comes from