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

Merge pull request #43255 from 0xff-dev/policy-limit-range 

[zh] sync policy/limit-range.md
pull/43257/head
Kubernetes Prow Robot 2023-09-29 01:46:42 -07:00 committed by GitHub
parent a9e769c55c 5fb0dc2379
commit fd033f4493
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/zh-cn/docs/concepts/policy/limit-range.md
View File

@ -103,14 +103,14 @@ For example, you define a `LimitRange` with this manifest:
例如，你使用如下清单定义一个 `LimitRange`：
{{% code file="concepts/policy/limit-range/problematic-limit-range.yaml" %}}
{{% code_sample file="concepts/policy/limit-range/problematic-limit-range.yaml" %}}
<!--
along with a Pod that declares a CPU resource request of `700m`, but not a limit:
-->
以及一个声明 CPU 资源请求为 `700m` 但未声明限制值的 Pod：
{{% code file="concepts/policy/limit-range/example-conflict-with-limitrange-cpu.yaml" %}}
{{% code_sample file="concepts/policy/limit-range/example-conflict-with-limitrange-cpu.yaml" %}}
<!--
then that Pod will not be scheduled, failing with an error similar to:
@ -126,7 +126,7 @@ If you set both `request` and `limit`, then that new Pod will be scheduled succe
-->
如果你同时设置了 `request` 和 `limit`，那么即使使用相同的 `LimitRange`，新 Pod 也会被成功调度：
{{% code file="concepts/policy/limit-range/example-no-conflict-with-limitrange-cpu.yaml" %}}
{{% code_sample file="concepts/policy/limit-range/example-no-conflict-with-limitrange-cpu.yaml" %}}
<!--
## Example resource constraints