fix error link of kubeadm init args (#17318)

This commit is contained in:
Luzhenxing
2019-11-05 13:12:38 +08:00
committed by Kubernetes Prow Robot
parent a7a4f9d4cb
commit e48b8693ae
2 changed files with 2 additions and 2 deletions
@@ -202,7 +202,7 @@ Static Pod manifest share a set of common properties:
* If using a local etcd server, `etcd-servers` address will be set to `127.0.0.1:2379`
- Leader election is enabled for both the controller-manager and the scheduler
- Controller-manager and the scheduler will reference kubeconfig files with their respective, unique identities
- All static Pods gets any extra flags specified by the user as described in [passing custom arguments to control plane components](/docs/reference/setup-tools/kubeadm/kubeadm-init/#custom-args)
- All static Pods gets any extra flags specified by the user as described in [passing custom arguments to control plane components](/docs/setup/production-environment/tools/kubeadm/control-plane-flags/)
- All static Pods gets any extra Volumes specified by the user (Host path)
Please note that:
@@ -151,7 +151,7 @@ For more information about `kubeadm init` arguments, see the [kubeadm reference
For a complete list of configuration options, see the [configuration file documentation](/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file).
To customize control plane components, including optional IPv6 assignment to liveness probe for control plane components and etcd server, provide extra arguments to each component as documented in [custom arguments](/docs/admin/kubeadm#custom-args).
To customize control plane components, including optional IPv6 assignment to liveness probe for control plane components and etcd server, provide extra arguments to each component as documented in [custom arguments](/docs/setup/production-environment/tools/kubeadm/control-plane-flags/).
To run `kubeadm init` again, you must first [tear down the cluster](#tear-down).