2.3 KiB
reviewers | title | content_type | weight | ||
---|---|---|---|---|---|
|
kubeadm config | concept | 50 |
During kubeadm init
, kubeadm uploads the ClusterConfiguration
object to your cluster
in a ConfigMap called kubeadm-config
in the kube-system
namespace. This configuration is then read during
kubeadm join
, kubeadm reset
and kubeadm upgrade
. To view this ConfigMap call kubeadm config view
.
You can use kubeadm config print
to print the default configuration and kubeadm config migrate
to
convert your old configuration files to a newer version. kubeadm config images list
and
kubeadm config images pull
can be used to list and pull the images that kubeadm requires.
For more information navigate to Using kubeadm init with a configuration file or Using kubeadm join with a configuration file.
You can also configure several kubelet-configuration options with kubeadm init
. These options will be the same on any node in your cluster.
See Configuring each kubelet in your cluster using kubeadm for details.
In Kubernetes v1.13.0 and later to list/pull kube-dns images instead of the CoreDNS image
the --config
method described here
has to be used.
kubeadm config print
{{< include "generated/kubeadm_config_print.md" >}}
kubeadm config print init-defaults
{{< include "generated/kubeadm_config_print_init-defaults.md" >}}
kubeadm config print join-defaults
{{< include "generated/kubeadm_config_print_join-defaults.md" >}}
kubeadm config migrate
{{< include "generated/kubeadm_config_migrate.md" >}}
kubeadm config images list
{{< include "generated/kubeadm_config_images_list.md" >}}
kubeadm config images pull
{{< include "generated/kubeadm_config_images_pull.md" >}}
{{% heading "whatsnext" %}}
- kubeadm upgrade to upgrade a Kubernetes cluster to a newer version