kubernetes/website

Guaranteed Scheduling For Critical Add-On Pods task does not link to details of built in PriorityClasses

Open

#39,000 opened on 2023年1月19日

GitHub で見る
 (7 comments) (0 reactions) (1 assignee)HTML (13,918 forks)batch import
help wantedlanguage/enpriority/backlogtriage/accepted

Repository metrics

Stars
 (4,127 stars)
PR merge metrics
 (平均マージ 16d 13h) (30d で 160 merged PRs)

説明

Folks - on this page, regarding this language: "To mark a Pod as critical, set priorityClassName for that Pod to system-cluster-critical or system-node-critical. system-node-critical is the highest available priority, even higher than system-cluster-critical." This immediately brings to mind the question: "what do you mean by even higher, i.e. what is the effect?" A little searching yields this documentation which answers the question nicely. Consider adding some clarification on the effect of node vs cluster priority in your docs.

コントリビューターガイド