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

Merge pull request #23007 from tengqm/links-setup

Browse Source 
Fix links in setup section
This commit is contained in:
Kubernetes Prow Robot
2020-08-07 01:26:19 -07:00
committed by GitHub
parent f73119c1a1 201f21715a
commit 821cce1a3a
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm.md
+1 -1
View File
@@ -31,7 +31,7 @@ when using kubeadm to set up a kubernetes cluster.
* Each host must [have docker, kubelet, and kubeadm installed](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/). * Each host must [have docker, kubelet, and kubeadm installed](/docs/setup/production-environment/tools/kubeadm/install-kubeadm/).
* Each host should have access to the Kubernetes container image registry (`k8s.gcr.io`) or list/pull the required etcd image using * Each host should have access to the Kubernetes container image registry (`k8s.gcr.io`) or list/pull the required etcd image using
`kubeadm config images list/pull`. This guide will setup etcd instances as `kubeadm config images list/pull`. This guide will setup etcd instances as
[static pods](https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/) managed by a kubelet. [static pods](/docs/tasks/configure-pod-container/static-pod/) managed by a kubelet.
* Some infrastructure to copy files between hosts. For example `ssh` and `scp` * Some infrastructure to copy files between hosts. For example `ssh` and `scp`
can satisfy this requirement. can satisfy this requirement.
content/en/docs/setup/production-environment/turnkey/gce.md
+1 -1
View File
@@ -122,7 +122,7 @@ kube-system kube-ui ClusterIP 10.0.0.3 <none>
... ...
``` ```
Similarly, you can take a look at the set of [pods](/docs/concepts/workloads/pods/pod/) that were created during cluster startup. Similarly, you can take a look at the set of [pods](/docs/concepts/workloads/pods/) that were created during cluster startup.
You can do this via the You can do this via the
```shell ```shell