kubernetes/website

Add actual priority values for built-in PriorityClasses to documentation

Open

#54,107 建立於 2026年1月23日

在 GitHub 查看
 (6 留言) (0 反應) (1 負責人)HTML (4,127 star) (13,918 fork)batch import
help wantedkind/featurelanguage/enpriority/backlogtriage/accepted

描述

This is a Feature Request

What would you like to be added

Add the actual priority values for the built-in PriorityClasses (system-cluster-critical and system-node-critical) to the Pod Priority and Preemption page.

Why is this needed?

The current documentation mentions these built-in PriorityClasses but doesn't specify their actual priority values:

  • system-node-critical: 2000001000
  • system-cluster-critical: 2000000000

Users can see these values by running kubectl get priorityclasses, but having them in the documentation would provide better context when choosing right priority values for custom PriorityClasses.

If this is valuable, /assign

貢獻者指南

技術棧
html
領域
documentation
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
無
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
90
研究方向
The issue asks to add priority values for system cluster critical and system node critical to the Pod Priority and Preemption documentation page. The exact values are 2000000000 and 2000001000 respectively. This requires editing the appropriate markdown file in the kubernetes/website repository, likely under content/en/docs/concepts/scheduling eviction/pod priority preemption.md. The contributor can verify the current file and add the values in the section discussing built in PriorityClasses.