2.0 KiB
| reviewers | title | content_template | weight | |||
|---|---|---|---|---|---|---|
|
kubeadm config | templates/concept | 50 |
{{% capture overview %}}
Beginning with v1.8.0, kubeadm uploads the configuration of your cluster to a ConfigMap called
kubeadm-config in the kube-system namespace, and later reads the ConfigMap when upgrading.
This enables correct configuration of system components, and provides a seamless user experience.
You can execute kubeadm config view to view the ConfigMap. If you initialized your cluster using
kubeadm v1.7.x or lower, you must use kubeadm config upload to create the ConfigMap before you
may use kubeadm upgrade.
In Kubernetes v1.11.0, some new commands were added. You can use kubeadm config print-default
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.
{{% /capture %}}
{{% capture body %}}
kubeadm config upload from-file
{{< include "generated/kubeadm_config_upload_from-file.md" >}}
kubeadm config upload from-flags
{{< include "generated/kubeadm_config_upload_from-flags.md" >}}
kubeadm config view
{{< include "generated/kubeadm_config_view.md" >}}
kubeadm config print-default
{{< include "generated/kubeadm_config_print-default.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" >}}
{{% /capture %}}
{{% capture whatsnext %}}
- kubeadm upgrade to upgrade a Kubernetes cluster to a newer version {{% /capture %}}