You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -95,10 +95,10 @@ Examples of policies that could be created using limit range are:
95
95
- Define default CPU limit and request to 150m and memory default request to 300Mi for Containers started with no cpu and memory requests in their specs.
96
96
-->
97
97
98
-
能够使用 LimitRange 的例子有:
98
+
能够使用限制范围创建策略的例子有:
99
99
100
-
- 在一个有两个节点,8 GiB 内存与16个核的集群中,限制一个命名空间的 Pod 申请100m单位,最大500m单位的CPU,以及申请200Mi,最大600Mi的内存。
101
-
- 为 spec 中没有 cpu 和内存需求值的 Container 定义默认 CPU 限制值与需求值150m,内存默认需求值300Mi。
100
+
- 在一个有两个节点,8 GiB 内存与16个核的集群中,限制一个命名空间的 Pod 申请 100m 单位,最大 500m 单位的 CPU,以及申请 200Mi,最大 600Mi 的内存。
101
+
- 为 spec 中没有 cpu 和内存需求值的 Container 定义默认 CPU 限制值与需求值 150m,内存默认需求值 300Mi。
102
102
103
103
<!--
104
104
In the case where the total limits of the namespace is less than the sum of the limits of the Pods/Containers,
@@ -111,7 +111,7 @@ there may be contention for resources. In this case, the Containers or Pods will
111
111
Neither contention nor changes to a LimitRange will affect already created resources.
112
112
-->
113
113
114
-
竞争和对 LimitRange 的改变都不会影响任何已经创建的资源。
114
+
竞争和对 LimitRange 的改变都不会影响任何已经创建了的资源。
115
115
116
116
<!--
117
117
## Examples
@@ -143,6 +143,6 @@ Neither contention nor changes to a LimitRange will affect already created resou
143
143
See [LimitRanger design doc](https://git.k8s.io/community/contributors/design-proposals/resource-management/admission_control_limit_range.md) for more information.
0 commit comments