From 2d4111833ce19c4d9510aabc110a8d80eec98f82 Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Fri, 28 Jul 2017 05:37:55 +0800 Subject: [PATCH] update version No. to para. (#4442) update version No. to para. --- docs/tasks/administer-cluster/cpu-memory-limit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/administer-cluster/cpu-memory-limit.md b/docs/tasks/administer-cluster/cpu-memory-limit.md index d04c9b14b4..41ef006437 100644 --- a/docs/tasks/administer-cluster/cpu-memory-limit.md +++ b/docs/tasks/administer-cluster/cpu-memory-limit.md @@ -103,7 +103,7 @@ deployment "nginx" created ``` Note that `kubectl run` creates a Deployment named "nginx" 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. The Deployment manages 1 replica of single container Pod. Let's take a look at the Pod it manages. First, find the name of the Pod: ```shell