kubernetes/website

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

Open

#39.000 geöffnet am 19. Jan. 2023

Auf GitHub ansehen
 (7 Kommentare) (0 Reaktionen) (1 zugewiesene Person)HTML (13.918 Forks)batch import
help wantedlanguage/enpriority/backlogtriage/accepted

Repository-Metriken

Stars
 (4.127 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 16T 13h) (160 gemergte PRs in 30 T)

Beschreibung

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.

Contributor Guide