whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove stale docs about disabling the PodPriority feature.

Browse Source 
As of 1.18 the PodPriority feature cannot be disabled, so update
the docs to reflect this.
This commit is contained in:
Chris Friesen
2020-04-27 11:47:50 -06:00
parent ceecb1667e
commit f768f14567
1 changed files with 1 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/configuration/pod-priority-preemption.md
+1 -8
View File
@@ -51,13 +51,6 @@ Kubernetes already ships with two PriorityClasses:
These are common classes and are used to [ensure that critical components are always scheduled first](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/). These are common classes and are used to [ensure that critical components are always scheduled first](/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/).
{{< /note >}} {{< /note >}}
If you try the feature and then decide to disable it, you must remove the
PodPriority command-line flag or set it to `false`, and then restart the API
server and scheduler. After the feature is disabled, the existing Pods keep
their priority fields, but preemption is disabled, and priority fields are
ignored. If the feature is disabled, you cannot set `priorityClassName` in new
Pods.
## How to disable preemption ## How to disable preemption
{{< caution >}} {{< caution >}}
@@ -120,7 +113,7 @@ cluster when they should use this PriorityClass.
### Notes about PodPriority and existing clusters ### Notes about PodPriority and existing clusters
- If you upgrade your existing cluster and enable this feature, the priority - If you upgrade an existing cluster without this feature, the priority
of your existing Pods is effectively zero. of your existing Pods is effectively zero.
- Addition of a PriorityClass with `globalDefault` set to `true` does not - Addition of a PriorityClass with `globalDefault` set to `true` does not