From b01e8ae1f4a218365c33e913cd3d0bb5bb062e60 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Fri, 29 Sep 2017 14:20:40 -0700 Subject: [PATCH] Replace v1.7 with {{page.version}}. (#5691) --- docs/tasks/administer-cluster/quota-api-object.md | 4 ++-- docs/tasks/administer-cluster/quota-memory-cpu-namespace.md | 2 +- docs/tasks/administer-cluster/quota-pod-namespace.md | 2 +- docs/tasks/configure-pod-container/assign-cpu-resource.md | 2 +- docs/tasks/configure-pod-container/assign-memory-resource.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/tasks/administer-cluster/quota-api-object.md b/docs/tasks/administer-cluster/quota-api-object.md index c40566f050..fd3fdd2236 100644 --- a/docs/tasks/administer-cluster/quota-api-object.md +++ b/docs/tasks/administer-cluster/quota-api-object.md @@ -9,7 +9,7 @@ This page shows how to configure quotas for API objects, including PersistentVolumeClaims and Services. A quota restricts the number of objects, of a particular type, that can be created in a namespace. You specify quotas in a -[ResourceQuota](/docs/api-reference/v1.7/#resourcequota-v1-core) +[ResourceQuota](/docs/api-reference/{{page.version}}/#resourcequota-v1-core) object. {% endcapture %} @@ -53,7 +53,7 @@ kubectl get resourcequota object-quota-demo --namespace=quota-object-example --o The output shows that in the quota-object-example namespace, there can be at most one PersistentVolumeClaim, at most two Services of type LoadBalancer, and no Services -of type NodePort. +of type NodePort. ```yaml status: diff --git a/docs/tasks/administer-cluster/quota-memory-cpu-namespace.md b/docs/tasks/administer-cluster/quota-memory-cpu-namespace.md index 75d71d4f07..1b7118ca44 100644 --- a/docs/tasks/administer-cluster/quota-memory-cpu-namespace.md +++ b/docs/tasks/administer-cluster/quota-memory-cpu-namespace.md @@ -7,7 +7,7 @@ title: Configure Memory and CPU Quotas for a Namespace This page shows how to set quotas for the total amount memory and CPU that can be used by all Containers running in a namespace. You specify quotas in a -[ResourceQuota](/docs/api-reference/v1.7/#resourcequota-v1-core) +[ResourceQuota](/docs/api-reference/{{page.version}}/#resourcequota-v1-core) object. {% endcapture %} diff --git a/docs/tasks/administer-cluster/quota-pod-namespace.md b/docs/tasks/administer-cluster/quota-pod-namespace.md index dc11c232b9..9933beaf72 100644 --- a/docs/tasks/administer-cluster/quota-pod-namespace.md +++ b/docs/tasks/administer-cluster/quota-pod-namespace.md @@ -7,7 +7,7 @@ title: Configure a Pod Quota for a Namespace This page shows how to set a quota for the total number of Pods that can run in a namespace. You specify quotas in a -[ResourceQuota](/docs/api-reference/v1.7/#resourcequota-v1-core) +[ResourceQuota](/docs/api-reference/{{page.version}}/#resourcequota-v1-core) object. {% endcapture %} diff --git a/docs/tasks/configure-pod-container/assign-cpu-resource.md b/docs/tasks/configure-pod-container/assign-cpu-resource.md index 81da766f98..c99321a9af 100644 --- a/docs/tasks/configure-pod-container/assign-cpu-resource.md +++ b/docs/tasks/configure-pod-container/assign-cpu-resource.md @@ -219,7 +219,7 @@ could use all of the CPU resources available on the Node where it is running. * The Container is running in a namespace that has a default CPU limit, and the Container is automatically assigned the default limit. Cluster administrators can use a -[LimitRange](https://kubernetes.io/docs/api-reference/v1.7/#limitrange-v1-core/) +[LimitRange](https://kubernetes.io/docs/api-reference/{{page.version}}/#limitrange-v1-core/) to specify a default value for the CPU limit. ## Motivation for CPU requests and limits diff --git a/docs/tasks/configure-pod-container/assign-memory-resource.md b/docs/tasks/configure-pod-container/assign-memory-resource.md index bc3a4bf908..7fda6fd170 100644 --- a/docs/tasks/configure-pod-container/assign-memory-resource.md +++ b/docs/tasks/configure-pod-container/assign-memory-resource.md @@ -313,7 +313,7 @@ could use all of the memory available on the Node where it is running. * The Container is running in a namespace that has a default memory limit, and the Container is automatically assigned the default limit. Cluster administrators can use a -[LimitRange](https://kubernetes.io/docs/api-reference/v1.7/#limitrange-v1-core) +[LimitRange](https://kubernetes.io/docs/api-reference/{{page.version}}/#limitrange-v1-core) to specify a default value for the memory limit. ## Motivation for memory requests and limits