fix direct link in docs/concepts/configuration/pod-priority-preemption (#8854)

This commit is contained in:
lovejoy
2018-06-02 10:40:00 +08:00
committed by k8s-ci-robot
parent 9ddca8982a
commit 5e4096b184
@@ -173,7 +173,7 @@ Pod P. By doing this, scheduler makes Pod P eligible to preempt Pods on another
#### Graceful termination of preemption victims #### Graceful termination of preemption victims
When Pods are preempted, the victims get their When Pods are preempted, the victims get their
[graceful termination period](https://kubernetes.io/docs/concepts/workloads/pods/pod/#termination-of-pods). [graceful termination period](/docs/concepts/workloads/pods/pod/#termination-of-pods).
They have that much time to finish their work and exit. If they don't, they are They have that much time to finish their work and exit. If they don't, they are
killed. This graceful termination period creates a time gap between the point killed. This graceful termination period creates a time gap between the point
that the scheduler preempts Pods and the time when the pending Pod (P) can be that the scheduler preempts Pods and the time when the pending Pod (P) can be
@@ -186,7 +186,7 @@ to zero or a small number.
#### PodDisruptionBudget is supported, but not guaranteed! #### PodDisruptionBudget is supported, but not guaranteed!
A [Pod Disruption Budget (PDB)](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/) A [Pod Disruption Budget (PDB)](/docs/concepts/workloads/pods/disruptions/)
allows application owners to limit the number Pods of a replicated application that allows application owners to limit the number Pods of a replicated application that
are down simultaneously from voluntary disruptions. Kubernetes 1.9 supports PDB are down simultaneously from voluntary disruptions. Kubernetes 1.9 supports PDB
when preempting Pods, but respecting PDB is best effort. The Scheduler tries to when preempting Pods, but respecting PDB is best effort. The Scheduler tries to