Skip to content

Commit 1075d2b

Browse files
committed
Update pod-priority-preemption.md
1 parent c97178c commit 1075d2b

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

content/zh-cn/docs/concepts/scheduling-eviction/pod-priority-preemption.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -108,9 +108,10 @@ PriorityClass 对象的名称必须是有效的
108108

109109
<!--
110110
A PriorityClass object can have any 32-bit integer value smaller than or equal
111-
to 1 billion. Larger numbers are reserved for critical system Pods that should
112-
not normally be preempted or evicted. A cluster admin should create one
113-
PriorityClass object for each such mapping that they want.
111+
to 1 billion. This means that the range of values for a PriorityClass object is
112+
from -2147483648 to 1000000000 inclusive. Larger numbers are reserved for
113+
built-in PriorityClasses that represent critical system Pods. A cluster
114+
admin should create one PriorityClass object for each such mapping that they want.
114115
115116
PriorityClass also has two optional fields: `globalDefault` and `description`.
116117
The `globalDefault` field indicates that the value of this PriorityClass should
@@ -123,7 +124,8 @@ The `description` field is an arbitrary string. It is meant to tell users of the
123124
cluster when they should use this PriorityClass.
124125
-->
125126
PriorityClass 对象可以设置任何小于或等于 10 亿的 32 位整数值。
126-
较大的数字是为通常不应被抢占或驱逐的关键的系统 Pod 所保留的。
127+
这意味着 PriorityClass 对象的值范围是 从 -2147483648 到 1000000000(含)。
128+
较大的数字保留用于代表关键系统 Pod 的内置 PriorityClasses。
127129
集群管理员应该为这类映射分别创建独立的 PriorityClass 对象。
128130

129131
PriorityClass 还有两个可选字段:`globalDefault``description`

0 commit comments

Comments
 (0)