whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

kubeadm-config.md: update the page to reflect current state

Browse Source 
We have seen a number of questions around the usage of "config print".
Clarify the usage of this command. Add a note that the output should
not be taken literally.

Link to the "customizing components" page instead of the "kubelet
integration" page. The former already links to the later.

Remove note about kube-dns which hasn't been supported for a while.
This commit is contained in:
Lubomir I. Ivanov
2021-10-27 00:32:49 +03:00
parent 88cec414e7
commit 586b359b05
1 changed files with 16 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/setup-tools/kubeadm/kubeadm-config.md
+16 -9
View File
@@ -12,20 +12,27 @@ During `kubeadm init`, kubeadm uploads the `ClusterConfiguration` object to your
in a ConfigMap called `kubeadm-config` in the `kube-system` namespace. This configuration is then read during in a ConfigMap called `kubeadm-config` in the `kube-system` namespace. This configuration is then read during
`kubeadm join`, `kubeadm reset` and `kubeadm upgrade`. `kubeadm join`, `kubeadm reset` and `kubeadm upgrade`.
You can use `kubeadm config print` to print the default configuration and `kubeadm config migrate` to You can use `kubeadm config print` to print the default static configuration that kubeadm
convert your old configuration files to a newer version. `kubeadm config images list` and uses for `kubeadm init` and `kubeadm join`.
`kubeadm config images pull` can be used to list and pull the images that kubeadm requires.
For more information navigate to {{< note >}}
The output of the command is meant to serve as an example. You must manually edit the output
of this command to adapt to your setup. Remove the fields that you are not certain about and kubeadm
will try to default them on runtime by examining the host.
{{< /note >}}
For more information on `init` and `join` navigate to
[Using kubeadm init with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file) [Using kubeadm init with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file)
or [Using kubeadm join with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-join/#config-file). or [Using kubeadm join with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-join/#config-file).
You can also configure several kubelet-configuration options with `kubeadm init`. These options will be the same on any node in your cluster. For more information on using the kubeadm configuration API navigate to
See [Configuring each kubelet in your cluster using kubeadm](/docs/setup/production-environment/tools/kubeadm/kubelet-integration/) for details. [Customizing components with the kubeadm API](/docs/setup/production-environment/tools/kubeadm/control-plane-flags).
In Kubernetes v1.13.0 and later to list/pull kube-dns images instead of the CoreDNS image You can use `kubeadm config migrate` to convert your old configuration files that contain a deprecated
the `--config` method described [here](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-addon) API version to a newer, supported API version.
has to be used.
`kubeadm config images list` and `kubeadm config images pull` can be used to list and pull the images
that kubeadm requires.
<!-- body --> <!-- body -->
## kubeadm config print {#cmd-config-print} ## kubeadm config print {#cmd-config-print}