whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Replace v1.7 with {{page.version}}. (#5691)

Browse Source
This commit is contained in:
Steve Perry
2017-09-29 14:20:40 -07:00
committed by GitHub
parent 85fad8f150
commit b01e8ae1f4
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-cluster/quota-api-object.md
+2 -2
View File
@@ -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:
docs/tasks/administer-cluster/quota-memory-cpu-namespace.md
+1 -1
View File
@@ -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 %}
docs/tasks/administer-cluster/quota-pod-namespace.md
+1 -1
View File
@@ -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 %}
docs/tasks/configure-pod-container/assign-cpu-resource.md
+1 -1
View File
@@ -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
docs/tasks/configure-pod-container/assign-memory-resource.md
+1 -1
View File
@@ -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