From 64a3f7ab2e21f673e8cd1dc886b57bdf1deead63 Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Sat, 8 Jul 2017 05:20:22 +0800 Subject: [PATCH] logging.md: replace v1.6 with page.version logging.md: replace v1.6 with page.version --- docs/concepts/cluster-administration/logging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/cluster-administration/logging.md b/docs/concepts/cluster-administration/logging.md index edc81b770a..13773c90fd 100644 --- a/docs/concepts/cluster-administration/logging.md +++ b/docs/concepts/cluster-administration/logging.md @@ -49,7 +49,7 @@ $ kubectl logs counter ... ``` -You can use `kubectl logs` to retrieve logs from a previous instantiation of a container with `--previous` flag, in case the container has crashed. If your pod has multiple containers, you should specify which container's logs you want to access by appending a container name to the command. See the [`kubectl logs` documentation](/docs/user-guide/kubectl/v1.6/#logs) for more details. +You can use `kubectl logs` to retrieve logs from a previous instantiation of a container with `--previous` flag, in case the container has crashed. If your pod has multiple containers, you should specify which container's logs you want to access by appending a container name to the command. See the [`kubectl logs` documentation](/docs/user-guide/kubectl/{{page.version}}/#logs) for more details. ## Logging at the node level @@ -77,7 +77,7 @@ As an example, you can find detailed information about how `kube-up.sh` sets up logging for COS image on GCP in the corresponding [script] [cosConfigureHelper]. -When you run [`kubectl logs`](/docs/user-guide/kubectl/v1.6/#logs) as in +When you run [`kubectl logs`](/docs/user-guide/kubectl/{{page.version}}/#logs) as in the basic logging example, the kubelet on the node handles the request and reads directly from the log file, returning the contents in the response. **Note:** currently, if some external system has performed the rotation,