Skip to content

Commit cbfeb8b

Browse files
authored
Merge pull request #37027 from Amrita42/Amrita-BZ1959689
Added "limit" to the definition of max resource constraint for containers
2 parents e726770 + 3c21d16 commit cbfeb8b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

modules/nodes-cluster-limit-ranges-limits.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ the container CPU and memory requests in the `Pod` spec must comply with the val
2020
* The container CPU or memory request and limit must be greater than or equal to the
2121
`min` resource constraint for containers that are specified in the `LimitRange` object.
2222

23-
* The container CPU or memory request must be less than or equal to the
23+
* The container CPU or memory request and limit must be less than or equal to the
2424
`max` resource constraint for containers that are specified in the `LimitRange` object.
2525
+
2626
If the `LimitRange` object defines a `max` CPU, you do not need to define a CPU
@@ -88,7 +88,7 @@ spec:
8888
A limit range allows you to specify the minimum and maximum CPU and memory limits for all containers
8989
across a pod in a given project. To create a container in the project, the container CPU and memory
9090
requests in the `Pod` spec must comply with the values set in the `LimitRange` object. If not,
91-
the pod does not get created.
91+
the pod does not get created.
9292

9393
If the `Pod` spec does not specify a container resource memory or limit,
9494
the `default` or `defaultRequest` CPU and memory values for containers

0 commit comments

Comments
 (0)