sync /scheduling-eviction/_index.md logging flow-control

Author: asa3311

content/zh-cn/docs/concepts/cluster-administration/flow-control.md

@@ -831,7 +831,7 @@ that originate from outside your cluster.
 则可以配置规则，阻止所有来自集群外部的健康检查请求。
 {{< /caution >}}
 
-{{< codenew file="priority-and-fairness/health-for-strangers.yaml" >}}
+{{% codenew file="priority-and-fairness/health-for-strangers.yaml" %}}
 
 <!--
 ## Diagnostics

content/zh-cn/docs/concepts/cluster-administration/logging.md

@@ -69,7 +69,7 @@ Kubernetes 从正在运行的 Pod 中捕捉每个容器的日志。
 
 此示例使用带有一个容器的 `Pod` 的清单，该容器每秒将文本写入标准输出一次。
 
-{{< codenew file="debug/counter-pod.yaml" >}}
+{{% codenew file="debug/counter-pod.yaml" %}}
 
 <!--
 To run this pod, use the following command:
@@ -463,7 +463,7 @@ manifest for the Pod:
 例如，某 Pod 中运行一个容器，且该容器使用两个不同的格式写入到两个不同的日志文件。
 下面是这个 Pod 的清单：
 
-{{< codenew file="admin/logging/two-files-counter-pod.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod.yaml" %}}
 
 <!--
 It is not recommended to write log entries with different formats to the same log
@@ -481,7 +481,7 @@ Here's a manifest for a pod that has two sidecar containers:
 -->
 下面是运行两个边车容器的 Pod 的清单：
 
-{{< codenew file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" %}}
 
 <!--
 Now when you run this pod, you can access each log stream separately by
@@ -619,7 +619,7 @@ to configure fluentd.
 第一个文件包含用来配置 fluentd 的
 [ConfigMap](/zh-cn/docs/tasks/configure-pod-container/configure-pod-configmap/)。
 
-{{< codenew file="admin/logging/fluentd-sidecar-config.yaml" >}}
+{{% codenew file="admin/logging/fluentd-sidecar-config.yaml" %}}
 
 {{< note >}}
 <!--
@@ -636,7 +636,7 @@ The pod mounts a volume where fluentd can pick up its configuration data.
 第二个清单描述了一个运行 fluentd 边车容器的 Pod。
 该 Pod 挂载一个卷，flutend 可以从这个卷上拣选其配置数据。
 
-{{< codenew file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" >}}
+{{% codenew file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" %}}
 
 <!--
 ### Exposing logs directly from the application

content/zh-cn/docs/concepts/scheduling-eviction/_index.md

@@ -50,6 +50,7 @@ of terminating one or more Pods on Nodes.
 * [Scheduler Performance Tuning](/docs/concepts/scheduling-eviction/scheduler-perf-tuning/)
 * [Resource Bin Packing for Extended Resources](/docs/concepts/scheduling-eviction/resource-bin-packing/)
 * [Pod Scheduling Readiness](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/)
+* [Descheduler](https://github.com/kubernetes-sigs/descheduler#descheduler-for-kubernetes)
 -->
 
 ## 调度
@@ -64,6 +65,7 @@ of terminating one or more Pods on Nodes.
 * [调度器性能调试](/zh-cn/docs/concepts/scheduling-eviction/scheduler-perf-tuning/)
 * [扩展资源的资源装箱](/zh-cn/docs/concepts/scheduling-eviction/resource-bin-packing/)
 * [Pod 调度就绪](/zh-cn/docs/concepts/scheduling-eviction/pod-scheduling-readiness/)
+* [Descheduler](https://github.com/kubernetes-sigs/descheduler#descheduler-for-kubernetes)
 
 <!--
 ## Pod Disruption