"catch-all" priority-level only gets a minimal positive share of concurrency and won't be reaching ideally unless you intentionally deleted the suggested "global-default".

"exempt" priority-level is used for preventing priority inversion and ensuring that sysadmin requests are always possible.

The objects that define an apiserver's initial behavior.

Mandatory PriorityLevelConfiguration objects.

Mandatory PriorityLevelConfiguration objects.

The objects that define an apiserver's initial behavior.

We add an explicit rule for endpoint-controller with high precedence to ensure that those calls won't get caught by the following <workload-leader-election> flow-schema.

Suggested FlowSchema objects.

Suggested FlowSchema objects.

Suggested FlowSchema objects.

Suggested FlowSchema objects.

the following flow schema exempts probes.

The objects that define the current suggested additional configuration.

Suggested FlowSchema objects.

Suggested FlowSchema objects.

Suggested FlowSchema objects.

Suggested FlowSchema objects.

TODO(#80289): Get rid of this rule once we get rid of support for using endpoints and configmaps objects for leader election.

global-default priority-level.

leader-election priority-level.

Suggested PriorityLevelConfiguration objects.

The objects that define the current suggested additional configuration.

system priority-level.

workload-high priority-level.

workload-low priority-level.