kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #46694 from JoeyC-Dev/patch-1 

Increase readability by refining the wording
pull/47053/head
Kubernetes Prow Robot 2024-07-19 05:43:09 -07:00 committed by GitHub
parent 11f48b6716 6bba180fe7
commit 2ac912a107
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
content/en/docs/tasks/administer-cluster/cpu-management-policies.md
View File

@ -165,7 +165,7 @@ spec:
image: nginx
```
This pod runs in the `BestEffort` QoS class because no resource `requests` or
The pod above runs in the `BestEffort` QoS class because no resource `requests` or
`limits` are specified. It runs in the shared pool.
```yaml
@ -180,7 +180,7 @@ spec:
memory: "100Mi"
```
This pod runs in the `Burstable` QoS class because resource `requests` do not
The pod above runs in the `Burstable` QoS class because resource `requests` do not
equal `limits` and the `cpu` quantity is not specified. It runs in the shared
pool.
@ -198,7 +198,7 @@ spec:
cpu: "1"
```
This pod runs in the `Burstable` QoS class because resource `requests` do not
The pod above runs in the `Burstable` QoS class because resource `requests` do not
equal `limits`. It runs in the shared pool.
```yaml
@ -215,7 +215,7 @@ spec:
cpu: "2"
```
This pod runs in the `Guaranteed` QoS class because `requests` are equal to `limits`.
The pod above runs in the `Guaranteed` QoS class because `requests` are equal to `limits`.
And the container's resource limit for the CPU resource is an integer greater than
or equal to one. The `nginx` container is granted 2 exclusive CPUs.
@ -234,7 +234,7 @@ spec:
cpu: "1.5"
```
This pod runs in the `Guaranteed` QoS class because `requests` are equal to `limits`.
The pod above runs in the `Guaranteed` QoS class because `requests` are equal to `limits`.
But the container's resource limit for the CPU resource is a fraction. It runs in
the shared pool.
@ -250,7 +250,7 @@ spec:
cpu: "2"
```
This pod runs in the `Guaranteed` QoS class because only `limits` are specified
The pod above runs in the `Guaranteed` QoS class because only `limits` are specified
and `requests` are set equal to `limits` when not explicitly specified. And the
container's resource limit for the CPU resource is an integer greater than or
equal to one. The `nginx` container is granted 2 exclusive CPUs.