From e4c3319ad36b0ac3690d4de86f9cd7a0d345f4c7 Mon Sep 17 00:00:00 2001
From: Zhang Yong <npu21@163.com>
Date: Mon, 28 Sep 2020 17:39:02 +0800
Subject: [PATCH] add post-filter part

---
 .../scheduling-eviction/scheduling-framework.md  | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/content/zh/docs/concepts/scheduling-eviction/scheduling-framework.md b/content/zh/docs/concepts/scheduling-eviction/scheduling-framework.md
index 4b3cfd6627..8d17592937 100644
--- a/content/zh/docs/concepts/scheduling-eviction/scheduling-framework.md
+++ b/content/zh/docs/concepts/scheduling-eviction/scheduling-framework.md
@@ -156,6 +156,22 @@ called for that node. Nodes may be evaluated concurrently.
 
 过滤插件用于过滤出不能运行该 Pod 的节点。对于每个节点，调度器将按照其配置顺序调用这些过滤插件。如果任何过滤插件将节点标记为不可行，则不会为该节点调用剩下的过滤插件。节点可以被同时进行评估。
 
+<!--
+### PostFilter {#post-filter}
+-->
+
+### 后置过滤 {#post-filter}
+
+<!--
+These plugins are called after Filter phase, but only when no feasible nodes
+were found for the pod. Plugins are called in their configured order. If
+any postFilter plugin marks the node as `Schedulable`, the remaining plugins
+will not be called. A typical PostFilter implementation is preemption, which
+tries to make the pod schedulable by preempting other Pods.
+-->
+
+这些插件在筛选阶段后调用，但仅在该pod没有可行的节点时调用。插件按其配置的顺序调用。如果任何后过滤器插件标记节点为“可调度”， 则其余的插件不会调用。典型的后筛选实现是抢占，试图通过抢占其他pod的资源使该pod可以调度。
+
 <!-- 
 ### PreScore {#pre-score}
  -->