Fix broken links (#3353)

Fix broken links
This commit is contained in:
Xiaoyu Zhang
2017-04-13 06:42:04 +08:00
committed by Andrew Chen
parent da5308a10f
commit 965e095e52
@@ -97,7 +97,7 @@ and a [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/).
{% include code.html language="yaml" file="zookeeper.yaml" ghlink="/docs/tutorials/stateful-application/zookeeper.yaml" %} {% include code.html language="yaml" file="zookeeper.yaml" ghlink="/docs/tutorials/stateful-application/zookeeper.yaml" %}
Open a command terminal, and use Open a command terminal, and use
[`kubectl create`](/docs/user-guide/kubectl/kubectl_create/) to create the [`kubectl create`](/docs/user-guide/kubectl/v1.6/#create) to create the
manifest. manifest.
```shell ```shell
@@ -114,7 +114,7 @@ poddisruptionbudget "zk-budget" created
statefulset "zk" created statefulset "zk" created
``` ```
Use [`kubectl get`](/docs/user-guide/kubectl/kubectl_get/) to watch the Use [`kubectl get`](/docs/user-guide/kubectl/v1.6/#get) to watch the
StatefulSet controller create the StatefulSet's Pods. StatefulSet controller create the StatefulSet's Pods.
```shell ```shell
@@ -153,7 +153,7 @@ leader election. Each server in the ensemble needs to have a unique
identifier, all servers need to know the global set of identifiers, and each identifier, all servers need to know the global set of identifiers, and each
identifier needs to be associated with a network address. identifier needs to be associated with a network address.
Use [`kubectl exec`](/docs/user-guide/kubectl/kubectl_exec/) to get the hostnames Use [`kubectl exec`](/docs/user-guide/kubectl/v1.6/#exec) to get the hostnames
of the Pods in the `zk` StatefulSet. of the Pods in the `zk` StatefulSet.
```shell ```shell
@@ -356,7 +356,7 @@ in memory state, to storage media. Using WALs to provide durability is a common
technique for applications that use consensus protocols to achieve a replicated technique for applications that use consensus protocols to achieve a replicated
state machine and for storage applications in general. state machine and for storage applications in general.
Use [`kubectl delete`](/docs/user-guide/kubectl/kubectl_delete/) to delete the Use [`kubectl delete`](/docs/user-guide/kubectl/v1.6/#delete) to delete the
`zk` StatefulSet. `zk` StatefulSet.
```shell ```shell
@@ -681,7 +681,7 @@ log rotation for you. Kubernetes also implements a sane retention policy that
ensures application logs written to standard out and standard error do not ensures application logs written to standard out and standard error do not
exhaust local storage media. exhaust local storage media.
Use [`kubectl logs`](/docs/user-guide/kubectl/kubectl_logs/) to retrieve the last Use [`kubectl logs`](/docs/user-guide/kubectl/v1.6/#logs) to retrieve the last
few log lines from one of the Pods. few log lines from one of the Pods.
```shell ```shell
@@ -715,8 +715,8 @@ using `kubectl logs` and from the Kubernetes Dashboard.
``` ```
Kubernetes also supports more powerful, but more complex, logging integrations Kubernetes also supports more powerful, but more complex, logging integrations
with [Google Cloud Logging](https://github.com/kubernetes/contrib/blob/master/logging/fluentd-sidecar-gcp/README.md) with [Logging Using Stackdriver](/docs/tasks/debug-application-cluster/logging-stackdriver/)
and [ELK](https://github.com/kubernetes/contrib/blob/master/logging/fluentd-sidecar-es/README.md). and [Logging Using Elasticsearch and Kibana](/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana/).
For cluster level log shipping and aggregation, you should consider deploying a For cluster level log shipping and aggregation, you should consider deploying a
[sidecar](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html) [sidecar](http://blog.kubernetes.io/2015/06/the-distributed-system-toolkit-patterns.html)
container to rotate and ship your logs. container to rotate and ship your logs.
@@ -1022,7 +1022,7 @@ Get the nodes in your cluster.
kubectl get nodes kubectl get nodes
``` ```
Use [`kubectl cordon`](/docs/user-guide/kubectl/kubectl_cordon/) to Use [`kubectl cordon`](/docs/user-guide/kubectl/v1.6/#cordon) to
cordon all but four of the nodes in your cluster. cordon all but four of the nodes in your cluster.
```shell{% raw %} ```shell{% raw %}
@@ -1060,7 +1060,7 @@ kubernetes-minion-group-i4c4
{% endraw %} {% endraw %}
``` ```
Use [`kubectl drain`](/docs/user-guide/kubectl/kubectl_drain/) to cordon and Use [`kubectl drain`](/docs/user-guide/kubectl/v1.6/#drain) to cordon and
drain the node on which the `zk-0` Pod is scheduled. drain the node on which the `zk-0` Pod is scheduled.
```shell {% raw %} ```shell {% raw %}
@@ -1170,7 +1170,7 @@ dataLength = 5
numChildren = 0 numChildren = 0
``` ```
Use [`kubectl uncordon`](/docs/user-guide/kubectl/kubectl_uncordon/) to uncordon the first node. Use [`kubectl uncordon`](/docs/user-guide/kubectl/v1.6/#uncordon) to uncordon the first node.
```shell ```shell
kubectl uncordon kubernetes-minion-group-pb41 kubectl uncordon kubernetes-minion-group-pb41