kubernetes/website

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

Open

#39.000 aberto em 19 de jan. de 2023

Ver no GitHub
 (7 comments) (0 reactions) (1 assignee)HTML (13.918 forks)batch import
help wantedlanguage/enpriority/backlogtriage/accepted

Métricas do repositório

Stars
 (4.127 stars)
Métricas de merge de PR
 (Mesclagem média 16d 13h) (160 fundiu PRs em 30d)

Description

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.

Guia do colaborador