Merge pull request #29621 from tengqm/fix-kubeadm-api-pointer

Fix kubeadm-config links
pull/29647/head
Kubernetes Prow Robot 2021-09-06 18:23:15 -07:00 committed by GitHub
commit b125d095ea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 5 additions and 5 deletions

View File

@ -144,7 +144,7 @@ install them selectively.
{{< /tabs >}} {{< /tabs >}}
For more details on each field in the `v1beta3` configuration you can navigate to our For more details on each field in the `v1beta3` configuration you can navigate to our
[API reference pages.] (https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3) [API reference pages.](/docs/reference/config-api/kubeadm-config.v1beta3/)
## {{% heading "whatsnext" %}} ## {{% heading "whatsnext" %}}

View File

@ -14,7 +14,7 @@ and kube-proxy you can use `KubeletConfiguration` and `KubeProxyConfiguration`,
All of these options are possible via the kubeadm configuration API. All of these options are possible via the kubeadm configuration API.
For more details on each field in the configuration you can navigate to our For more details on each field in the configuration you can navigate to our
[API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3). [API reference pages](/docs/reference/config-api/kubeadm-config.v1beta3/).
{{< note >}} {{< note >}}
Customizing the CoreDNS deployment of kubeadm is currently not supported. You must manually Customizing the CoreDNS deployment of kubeadm is currently not supported. You must manually
@ -202,7 +202,7 @@ For more details see [Configuring each kubelet in your cluster using kubeadm](/d
To customize kube-proxy you can pass a `KubeProxyConfiguration` next your `ClusterConfiguration` or To customize kube-proxy you can pass a `KubeProxyConfiguration` next your `ClusterConfiguration` or
`InitConfiguration` to `kubeadm init` separated by `---`. `InitConfiguration` to `kubeadm init` separated by `---`.
For more details you can navigate to our [API reference pages](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3). For more details you can navigate to our [API reference pages](/docs/reference/config-api/kubeadm-config.v1beta3/).
{{< note >}} {{< note >}}
kubeadm deploys kube-proxy as a {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}}, which means kubeadm deploys kube-proxy as a {{< glossary_tooltip text="DaemonSet" term_id="daemonset" >}}, which means

View File

@ -115,7 +115,7 @@ option. Your cluster requirements may need a different configuration.
{{< note >}} {{< note >}}
The `kubeadm init` flags `--config` and `--certificate-key` cannot be mixed, therefore if you want The `kubeadm init` flags `--config` and `--certificate-key` cannot be mixed, therefore if you want
to use the [kubeadm configuration](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3) to use the [kubeadm configuration](/docs/reference/config-api/kubeadm-config.v1beta3/)
you must add the `certificateKey` field in the appropriate config locations you must add the `certificateKey` field in the appropriate config locations
(under `InitConfiguration` and `JoinConfiguration: controlPlane`). (under `InitConfiguration` and `JoinConfiguration: controlPlane`).
{{< /note >}} {{< /note >}}

View File

@ -369,7 +369,7 @@ Kubernetes components like the kubelet and kube-controller-manager use the defau
for the feature to work. for the feature to work.
To workaround this issue you can configure the flex-volume directory using the kubeadm To workaround this issue you can configure the flex-volume directory using the kubeadm
[configuration file](https://godoc.org/k8s.io/kubernetes/cmd/kubeadm/app/apis/kubeadm/v1beta3). [configuration file](/docs/reference/config-api/kubeadm-config.v1beta3/).
On the primary control-plane Node (created using `kubeadm init`) pass the following On the primary control-plane Node (created using `kubeadm init`) pass the following
file using `--config`: file using `--config`: