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

Edits cpu-constraint-namespace.md

Browse Source 
- Removes stray link in middle of paragraph
- "cpu" becomes "CPU" throughout
This commit is contained in:
Ryan McGinnis
2017-09-11 09:09:46 -07:00
committed by Andrew Chen
parent 5a665549f2
commit 0ab5bb1432
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-cluster/cpu-constraint-namespace.md
+5 -5
View File
@@ -195,7 +195,7 @@ resources:
Because your Container did not specify its own CPU request and limit, it was given the Because your Container did not specify its own CPU request and limit, it was given the
[default CPU request and limit](/docs/tasks/administer-cluster/cpu-default-namespace/) [default CPU request and limit](/docs/tasks/administer-cluster/cpu-default-namespace/)
from the LimitRange. from the LimitRange.
* [Configure Memory and CPU Quotas for a Namespace](/docs/tasks/administer-cluster/quota-memory-cpu-namespace)
At this point, your Container might be running or it might not be running. Recall that a prerequisite At this point, your Container might be running or it might not be running. Recall that a prerequisite
for this task is that your Nodes have at least 1 CPU. If each of your Nodes has only for this task is that your Nodes have at least 1 CPU. If each of your Nodes has only
1 CPU, then there might not be enough allocatable CPU on any Node to accommodate a request 1 CPU, then there might not be enough allocatable CPU on any Node to accommodate a request
@@ -219,12 +219,12 @@ Pods that were created previously.
As a cluster administrator, you might want to impose restrictions on the CPU resources that Pods can use. As a cluster administrator, you might want to impose restrictions on the CPU resources that Pods can use.
For example: For example:
* Each Node in a cluster has 2 cpu. You do not want to accept any Pod that requests * Each Node in a cluster has 2 CPU. You do not want to accept any Pod that requests
more than 2 cpu, because no Node in the cluster can support the request. more than 2 CPU, because no Node in the cluster can support the request.
* A cluster is shared by your production and development departments. * A cluster is shared by your production and development departments.
You want to allow production workloads to consume up to 3 cpu, but you want development workloads to be limited You want to allow production workloads to consume up to 3 CPU, but you want development workloads to be limited
to 1 cpu. You create separate namespaces for production and development, and you apply CPU constraints to to 1 CPU. You create separate namespaces for production and development, and you apply CPU constraints to
each namespace. each namespace.
## Clean up ## Clean up