Skip to content

Commit 6a40a02

Browse files
authored
Merge pull request #37275 from kinzhi/kinzhi217
[zh-cn]Update memory-default-namespace.md
2 parents ea9befb + b837efe commit 6a40a02

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

content/zh-cn/docs/tasks/administer-cluster/manage-resources/memory-default-namespace.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -248,16 +248,16 @@ resources:
248248
```
249249

250250
{{< note >}}
251+
251252
<!--
252253
A `LimitRange` does **not** check the consistency of the default values it applies. This means that a default value for the _limit_ that is set by `LimitRange` may be less than the _request_ value specified for the container in the spec that a client submits to the API server. If that happens, the final Pod will not be scheduleable.
253254
See [Constraints on resource limits and requests](/docs/concepts/policy/limit-range/#constraints-on-resource-limits-and-requests) for more details.
254255
-->
255-
`LimitRange` **不会**去检查它所应用的默认值的一致性。这意味着由 `LimitRange`
256-
设置的 limit 的默认值可能小于客户端提交给 API 服务器的规约中为容器指定的请求值。
257-
如果发生这种情况,最终的 Pod 将无法被调度。
258-
更多的相关信息细节,请参考[对资源限制和请求的约束](/zh-cn/docs/concepts/policy/limit-range/)
259-
{{< /note >}}
256+
`LimitRange` **不会**检查它应用的默认值的一致性。 这意味着 `LimitRange` 设置的 _limit_ 的默认值可能小于客户端提交给
257+
API 服务器的声明中为容器指定的 _request_ 值。如果发生这种情况,最终会导致 Pod 无法调度。更多信息,
258+
请参阅[资源限制的 limit 和 request](/zh-cn/docs/concepts/policy/limit-range/#constraints-on-resource-limits-and-requests)
260259

260+
{{< /note >}}
261261

262262
<!--
263263
## Motivation for default memory limits and requests

0 commit comments

Comments
 (0)