Change API version to v1 in exmaples, plus minor tweaks (#13457)
This commit is contained in:
		
							parent
							
								
									91f73900db
								
							
						
					
					
						commit
						bbe35dcaae
					
				|  | @ -34,7 +34,7 @@ Kubernetes Version | Priority and Preemption State | Enabled by default | ||||||
| 1.9                | alpha                         | no | 1.9                | alpha                         | no | ||||||
| 1.10               | alpha                         | no | 1.10               | alpha                         | no | ||||||
| 1.11               | beta                          | yes | 1.11               | beta                          | yes | ||||||
| 1.14               | GA                            | yes | 1.14               | stable                        | yes | ||||||
| 
 | 
 | ||||||
| {{< warning >}}In a cluster where not all users are trusted, a | {{< warning >}}In a cluster where not all users are trusted, a | ||||||
| malicious user could create pods at the highest possible priorities, causing | malicious user could create pods at the highest possible priorities, causing | ||||||
|  | @ -136,7 +136,7 @@ cluster when they should use this PriorityClass. | ||||||
| ### Example PriorityClass | ### Example PriorityClass | ||||||
| 
 | 
 | ||||||
| ```yaml | ```yaml | ||||||
| apiVersion: scheduling.k8s.io/v1beta1 | apiVersion: scheduling.k8s.io/v1 | ||||||
| kind: PriorityClass | kind: PriorityClass | ||||||
| metadata: | metadata: | ||||||
|   name: high-priority |   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 | 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. | 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 | We may consider adding cross Node preemption in future versions if there is | ||||||
| algorithm with reasonable performance. We cannot promise anything at this point, | enough demand and if we find an algorithm with reasonable performance. | ||||||
| and cross Node preemption will not be considered a blocker for Beta or GA. |  | ||||||
| 
 | 
 | ||||||
| ## Debugging Pod Priority and Preemption | ## Debugging Pod Priority and Preemption | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue