kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Change API version to v1 in exmaples, plus minor tweaks (#13457)

pull/13482/head
Babak "Bobby" Salamat 2019-03-27 00:50:29 -07:00 committed by Qiming
parent 91f73900db
commit bbe35dcaae
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/en/docs/concepts/configuration/pod-priority-preemption.md
View File

@ -34,7 +34,7 @@ Kubernetes Version | Priority and Preemption State | Enabled by default
1.9 | alpha | no
1.10 | alpha | no
1.11 | beta | yes
1.14 | GA | yes
1.14 | stable | yes
{{< warning >}}In a cluster where not all users are trusted, a
malicious user could create pods at the highest possible priorities, causing
@ -136,7 +136,7 @@ cluster when they should use this PriorityClass.
### Example PriorityClass
```yaml
apiVersion: scheduling.k8s.io/v1beta1
apiVersion: scheduling.k8s.io/v1
kind: PriorityClass
metadata:
name: high-priority
@ -278,9 +278,8 @@ preempted. Here's an example:
If Pod Q were removed from its Node, the Pod anti-affinity violation would be
gone, and Pod P could possibly be scheduled on Node N.
We may consider adding cross Node preemption in future versions if we find an
algorithm with reasonable performance. We cannot promise anything at this point,
and cross Node preemption will not be considered a blocker for Beta or GA.
We may consider adding cross Node preemption in future versions if there is
enough demand and if we find an algorithm with reasonable performance.
## Debugging Pod Priority and Preemption