From 12bf9908b1366cbb87685c158697d675e6241307 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Fri, 29 Sep 2017 15:07:53 -0700 Subject: [PATCH] Replace v1.6 with {{page.version}}. (#5693) --- docs/tasks/administer-cluster/access-cluster-api.md | 2 +- docs/tasks/administer-cluster/access-cluster-services.md | 4 ++-- docs/tasks/administer-cluster/cluster-management.md | 2 +- docs/tasks/administer-cluster/cpu-constraint-namespace.md | 2 +- docs/tasks/administer-cluster/memory-constraint-namespace.md | 2 +- docs/tasks/administer-cluster/namespaces-walkthrough.md | 2 +- docs/tasks/configure-pod-container/configmap.md | 2 +- 7 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/tasks/administer-cluster/access-cluster-api.md b/docs/tasks/administer-cluster/access-cluster-api.md index 0eb4d059ca..0be8784993 100644 --- a/docs/tasks/administer-cluster/access-cluster-api.md +++ b/docs/tasks/administer-cluster/access-cluster-api.md @@ -55,7 +55,7 @@ Run it like this: $ kubectl proxy --port=8080 & ``` -See [kubectl proxy](/docs/user-guide/kubectl/v1.6/#proxy) for more details. +See [kubectl proxy](/docs/user-guide/kubectl/{{page.version}}/#proxy) for more details. Then you can explore the API with curl, wget, or a browser, like so: diff --git a/docs/tasks/administer-cluster/access-cluster-services.md b/docs/tasks/administer-cluster/access-cluster-services.md index 5c55fa3aca..8f3e41112e 100644 --- a/docs/tasks/administer-cluster/access-cluster-services.md +++ b/docs/tasks/administer-cluster/access-cluster-services.md @@ -27,7 +27,7 @@ You have several options for connecting to nodes, pods and services from outside - Access services through public IPs. - Use a service with type `NodePort` or `LoadBalancer` to make the service reachable outside the cluster. See the [services](/docs/user-guide/services) and - [kubectl expose](/docs/user-guide/kubectl/v1.6/#expose) documentation. + [kubectl expose](/docs/user-guide/kubectl/{{page.version}}/#expose) documentation. - Depending on your cluster environment, this may just expose the service to your corporate network, or it may expose it to the internet. Think about whether the service being exposed is secure. Does it do its own authentication? @@ -43,7 +43,7 @@ You have several options for connecting to nodes, pods and services from outside - Only works for HTTP/HTTPS. - Described [here](#manually-constructing-apiserver-proxy-urls). - Access from a node or pod in the cluster. - - Run a pod, and then connect to a shell in it using [kubectl exec](/docs/user-guide/kubectl/v1.6/#exec). + - Run a pod, and then connect to a shell in it using [kubectl exec](/docs/user-guide/kubectl/{{page.version}}/#exec). Connect to other nodes, pods, and services from that shell. - Some clusters may allow you to ssh to a node in the cluster. From there you may be able to access cluster services. This is a non-standard method, and will work on some clusters but diff --git a/docs/tasks/administer-cluster/cluster-management.md b/docs/tasks/administer-cluster/cluster-management.md index 3566ef2c6f..6bea6cde12 100644 --- a/docs/tasks/administer-cluster/cluster-management.md +++ b/docs/tasks/administer-cluster/cluster-management.md @@ -198,4 +198,4 @@ You can use `kubectl convert` command to convert config files between different kubectl convert -f pod.yaml --output-version v1 ``` -For more options, please refer to the usage of [kubectl convert](/docs/user-guide/kubectl/v1.6/#convert) command. +For more options, please refer to the usage of [kubectl convert](/docs/user-guide/kubectl/{{page.version}}/#convert) command. diff --git a/docs/tasks/administer-cluster/cpu-constraint-namespace.md b/docs/tasks/administer-cluster/cpu-constraint-namespace.md index 25681d77d7..40c4961832 100644 --- a/docs/tasks/administer-cluster/cpu-constraint-namespace.md +++ b/docs/tasks/administer-cluster/cpu-constraint-namespace.md @@ -7,7 +7,7 @@ title: Configure Minimum and Maximum CPU Constraints for a Namespace This page shows how to set minimum and maximum values for the CPU resources used by Containers and Pods in a namespace. You specify minimum and maximum CPU values in a -[LimitRange](/docs/api-reference/v1.6/#limitrange-v1-core) +[LimitRange](/docs/api-reference/{{page.version}}/#limitrange-v1-core) object. If a Pod does not meet the constraints imposed by the LimitRange, it cannot be created in the namespace. diff --git a/docs/tasks/administer-cluster/memory-constraint-namespace.md b/docs/tasks/administer-cluster/memory-constraint-namespace.md index c203f2e3d4..54e40a74c2 100644 --- a/docs/tasks/administer-cluster/memory-constraint-namespace.md +++ b/docs/tasks/administer-cluster/memory-constraint-namespace.md @@ -7,7 +7,7 @@ title: Configure Minimum and Maximum Memory Constraints for a Namespace This page shows how to set minimum and maximum values for memory used by Containers running in a namespace. You specify minimum and maximum memory values in a -[LimitRange](/docs/api-reference/v1.6/#limitrange-v1-core) +[LimitRange](/docs/api-reference/{{page.version}}/#limitrange-v1-core) object. If a Pod does not meet the constraints imposed by the LimitRange, it cannot be created in the namespace. diff --git a/docs/tasks/administer-cluster/namespaces-walkthrough.md b/docs/tasks/administer-cluster/namespaces-walkthrough.md index 6a6e47a37f..e327f20577 100644 --- a/docs/tasks/administer-cluster/namespaces-walkthrough.md +++ b/docs/tasks/administer-cluster/namespaces-walkthrough.md @@ -152,7 +152,7 @@ $ kubectl run snowflake --image=kubernetes/serve_hostname --replicas=2 ``` We have just created a deployment whose replica size is 2 that is running the pod called snowflake with a basic container that just serves the hostname. Note that `kubectl run` creates deployments only on Kubernetes cluster >= v1.2. If you are running older versions, it creates replication controllers instead. -If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/v1.6/#run) for more details. +If you want to obtain the old behavior, use `--generator=run/v1` to create replication controllers. See [`kubectl run`](/docs/user-guide/kubectl/{{page.version}}/#run) for more details. ```shell $ kubectl get deployment diff --git a/docs/tasks/configure-pod-container/configmap.md b/docs/tasks/configure-pod-container/configmap.md index 8236fd4ceb..71e1c39f49 100644 --- a/docs/tasks/configure-pod-container/configmap.md +++ b/docs/tasks/configure-pod-container/configmap.md @@ -36,7 +36,7 @@ The data source corresponds to a key-value pair in the ConfigMap, where * key = the file name or the key you provided on the command line, and * value = the file contents or the literal value you provided on the command line. -You can use [`kubectl describe`](/docs/user-guide/kubectl/v1.6/#describe) or [`kubectl get`](/docs/user-guide/kubectl/v1.6/#get) to retrieve information about a ConfigMap. The former shows a summary of the ConfigMap, while the latter returns the full contents of the ConfigMap. +You can use [`kubectl describe`](/docs/user-guide/kubectl/{{page.version}}/#describe) or [`kubectl get`](/docs/user-guide/kubectl/v1.6/#get) to retrieve information about a ConfigMap. The former shows a summary of the ConfigMap, while the latter returns the full contents of the ConfigMap. ### Create ConfigMaps from directories