From bee8feccc2a5068a26eb6af212b2f7fdad67fe30 Mon Sep 17 00:00:00 2001 From: Dipesh Rawat Date: Thu, 23 Feb 2023 17:39:00 +0000 Subject: [PATCH] Add minimum and maximum values for PriorityClass Co-authored-by: Tim Bannister --- .../concepts/scheduling-eviction/pod-priority-preemption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md b/content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md index b118649ddab85..d5607f48f5927 100644 --- a/content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md +++ b/content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md @@ -65,7 +65,7 @@ and it cannot be prefixed with `system-`. A PriorityClass object can have any 32-bit integer value smaller than or equal to 1 billion. This means that the range of values for a PriorityClass object is from -2147483648 to 1000000000 inclusive. Larger numbers are reserved for -critical system Pods that should not normally be preempted or evicted. A cluster +built-in PriorityClasses that represent critical system Pods. A cluster admin should create one PriorityClass object for each such mapping that they want. PriorityClass also has two optional fields: `globalDefault` and `description`.