Skip to content

Commit 586b359

Browse files
committed
kubeadm-config.md: update the page to reflect current state
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.
1 parent 88cec41 commit 586b359

File tree

1 file changed

+16
-9
lines changed

1 file changed

+16
-9
lines changed

content/en/docs/reference/setup-tools/kubeadm/kubeadm-config.md

Lines changed: 16 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,20 +12,27 @@ During `kubeadm init`, kubeadm uploads the `ClusterConfiguration` object to your
1212
in a ConfigMap called `kubeadm-config` in the `kube-system` namespace. This configuration is then read during
1313
`kubeadm join`, `kubeadm reset` and `kubeadm upgrade`.
1414

15-
You can use `kubeadm config print` to print the default configuration and `kubeadm config migrate` to
16-
convert your old configuration files to a newer version. `kubeadm config images list` and
17-
`kubeadm config images pull` can be used to list and pull the images that kubeadm requires.
15+
You can use `kubeadm config print` to print the default static configuration that kubeadm
16+
uses for `kubeadm init` and `kubeadm join`.
1817

19-
For more information navigate to
18+
{{< note >}}
19+
The output of the command is meant to serve as an example. You must manually edit the output
20+
of this command to adapt to your setup. Remove the fields that you are not certain about and kubeadm
21+
will try to default them on runtime by examining the host.
22+
{{< /note >}}
23+
24+
For more information on `init` and `join` navigate to
2025
[Using kubeadm init with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file)
2126
or [Using kubeadm join with a configuration file](/docs/reference/setup-tools/kubeadm/kubeadm-join/#config-file).
2227

23-
You can also configure several kubelet-configuration options with `kubeadm init`. These options will be the same on any node in your cluster.
24-
See [Configuring each kubelet in your cluster using kubeadm](/docs/setup/production-environment/tools/kubeadm/kubelet-integration/) for details.
28+
For more information on using the kubeadm configuration API navigate to
29+
[Customizing components with the kubeadm API](/docs/setup/production-environment/tools/kubeadm/control-plane-flags).
30+
31+
You can use `kubeadm config migrate` to convert your old configuration files that contain a deprecated
32+
API version to a newer, supported API version.
2533

26-
In Kubernetes v1.13.0 and later to list/pull kube-dns images instead of the CoreDNS image
27-
the `--config` method described [here](/docs/reference/setup-tools/kubeadm/kubeadm-init-phase/#cmd-phase-addon)
28-
has to be used.
34+
`kubeadm config images list` and `kubeadm config images pull` can be used to list and pull the images
35+
that kubeadm requires.
2936

3037
<!-- body -->
3138
## kubeadm config print {#cmd-config-print}

0 commit comments

Comments
 (0)