KUBERNETES(1)(kubernetes)
β¨ KUBERNETES(1) β kubeadm config images list β¨
okay bestie, welcome to the kubernetes manual, section 1 π
this one's filed under User manuals and it's literally all about peeking at the container images kubeadm is gonna pull. no cap.
πΈ NAME πΈ
kubeadm config images list β Print a list of images kubeadm will use. The configuration file is used in case any images or image repositories are customized π
π¦ SYNOPSIS π¦
kubeadm config images list [OPTIONS]
π DESCRIPTION π
Print a list of images kubeadm will use. The configuration file is used in case any images or image repositories are customized β¨
that's it. that's the whole vibe. it just tells you which images are coming to the party, and if you've customized your images or image repositories via a config file, it respects that. main character behavior honestly π
π OPTIONS π
--allow-missing-template-keys=trueβ If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats. (so it only cares when you're doinggolangorjsonpathstuff, iykyk)--config=""β Path to a kubeadm configuration file.--feature-gates=""β A set ofkey=valuepairs 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.-o,--output="text"β Output format. One of:text|json|yaml|kyaml|go-template|go-template-file|template|templatefile|jsonpath|jsonpath-as-json|jsonpath-file.--show-managed-fields=falseβ If true, keep the managedFields when printing objects in JSON or YAML format.
π«Ά OPTIONS INHERITED FROM PARENT COMMANDS π«Ά
these ones are lowkey just vibing here from the parent command, but they still count, bestie π
--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.--rootfs=""β The path to the 'real' host root filesystem. This will cause kubeadm to chroot into the provided path. (yes, chroot. it's giving committed π§)--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! π the way this manpage is literally a decade old and still serving...
and that's the whole page, bestie π go forth and list those images, you absolute icon β¨
source/version + date, as promised: this is from the KUBERNETES(1)(kubernetes) manual, filed under User manuals β originally compiled January 2015 by Eric Paris. 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