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

Fix Pod's property name (#7157)

reviewable/pr7220/r1
Bin Liu 2018-02-03 05:32:13 +08:00 committed by k8s-ci-robot
parent c1faa03370
commit aab6a69687
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/concepts/configuration/pod-priority-preemption.md
View File

@ -26,9 +26,9 @@ To use priority and preemption in Kubernetes 1.8 and later, follow these steps:
1. Add one or more PriorityClasses. 1. Add one or more PriorityClasses.
1. Create Pods with `PriorityClassName` set to one of the added PriorityClasses. 1. Create Pods with `priorityClassName` set to one of the added PriorityClasses.
Of course you do not need to create the Pods directly; normally you would add Of course you do not need to create the Pods directly; normally you would add
`PriorityClassName` to the Pod template of a collection object like a Deployment. `priorityClassName` to the Pod template of a collection object like a Deployment.
The following sections provide more information about these steps. The following sections provide more information about these steps.
@ -49,13 +49,13 @@ Also enable scheduling.k8s.io/v1alpha1 API and Priority [admission controller](/
``` ```
After the feature is enabled, you can create [PriorityClasses](#priorityclass) After the feature is enabled, you can create [PriorityClasses](#priorityclass)
and create Pods with [`PriorityClassName`](#pod-priority) set. and create Pods with [`priorityClassName`](#pod-priority) set.
If you try the feature and then decide to disable it, you must remove the PodPriority 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 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 scheduler. After the feature is disabled, the existing Pods keep their priority
fields, but preemption is disabled, and priority fields are ignored, and you fields, but preemption is disabled, and priority fields are ignored, and you
cannot set PriorityClassName in new Pods. cannot set `priorityClassName` in new Pods.
## PriorityClass ## PriorityClass
@ -71,9 +71,9 @@ object for each such mapping that they want.
PriorityClass also has two optional fields: `globalDefault` and `description`. PriorityClass also has two optional fields: `globalDefault` and `description`.
The `globalDefault` field indicates that the value of this PriorityClass should The `globalDefault` field indicates that the value of this PriorityClass should
be used for Pods without a `PriorityClassName`. Only one PriorityClass with be used for Pods without a `priorityClassName`. Only one PriorityClass with
`globalDefault` set to true can exist in the system. If there is no PriorityClass `globalDefault` set to true can exist in the system. If there is no PriorityClass
with `globalDefault` set, the priority of Pods with no `PriorityClassName` is zero. with `globalDefault` set, the priority of Pods with no `priorityClassName` is zero.
The `description` field is an arbitrary string. It is meant to tell users of The `description` field is an arbitrary string. It is meant to tell users of
the cluster when they should use this PriorityClass. the cluster when they should use this PriorityClass.