Skip to content

Commit 05464e0

Browse files
Mrunal PatelTim Bannister
andauthored
Update keps/sig-node/2712-pod-priority-based-graceful-node-shutdown/README.md
Co-authored-by: Tim Bannister <[email protected]>
1 parent 1aa704b commit 05464e0

File tree

1 file changed

+3
-2
lines changed
  • keps/sig-node/2712-pod-priority-based-graceful-node-shutdown

1 file changed

+3
-2
lines changed

keps/sig-node/2712-pod-priority-based-graceful-node-shutdown/README.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -154,8 +154,9 @@ e.g. the config could also be
154154
In the above case, the pods with custom-class-b will go into the same bucket
155155
as custom-class-c for shutdown.
156156

157-
If there are no pods in a particular range, then the kubelet will skip
158-
over the range entirely.
157+
If there are no pods in a particular range, then the kubelet does not wait
158+
for pods in that priority range. Instead, the kubelet immediately skips to the
159+
next priority class value range.
159160

160161
If this feature is enabled and no configuration is provided, then no ordering
161162
action will be taken. The rationale is to allow some users to opt out of this

0 commit comments

Comments
 (0)