kubernetes/website

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

Open

#39,000 opened on Jan 19, 2023

View on 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
 (Avg merge 16d 13h) (160 merged PRs in 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.

Contributor guide

Research direction
Research the difference between system node critical and system cluster critical priority classes in Kubernetes and suggest adding a clarification to the task page, possibly linking to the OpenShift documentation or the Kubernetes priority class concepts.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90