Merge pull request #42368 from my-git9/path-2678

[zh-cn]sync assign-pods-nodes-using-node-affinity configure-pod-initialization

Author: k8s-ci-robot

content/zh-cn/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity.md

@@ -109,7 +109,7 @@ This means that the pod will get scheduled only on a node that has a `disktype=s
 下面清单描述了一个 Pod，它有一个节点亲和性配置 `requiredDuringSchedulingIgnoredDuringExecution`，`disktype=ssd`。
 这意味着 pod 只会被调度到具有 `disktype=ssd` 标签的节点上。
 
-{{< codenew file="pods/pod-nginx-required-affinity.yaml" >}}
+{{% code file="pods/pod-nginx-required-affinity.yaml" %}}
 
 <!--
 1. Apply the manifest to create a Pod that is scheduled onto your
@@ -152,7 +152,7 @@ This means that the pod will prefer a node that has a `disktype=ssd` label.
 本清单描述了一个 Pod，它有一个节点亲和性设置 `preferredDuringSchedulingIgnoredDuringExecution`，`disktype: ssd`。
 这意味着 Pod 将首选具有 `disktype=ssd` 标签的节点。
 
-{{< codenew file="pods/pod-nginx-preferred-affinity.yaml" >}}
+{{% code file="pods/pod-nginx-preferred-affinity.yaml" %}}
 
 <!--
 1. Apply the manifest to create a Pod that is scheduled onto your

content/zh-cn/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md

@@ -102,7 +102,7 @@ Kubernetes 提供了存活探针来发现并处理这种情况。
 在本练习中，你会创建一个 Pod，其中运行一个基于 `registry.k8s.io/busybox` 镜像的容器。
 下面是这个 Pod 的配置文件。
 
-{{< codenew file="pods/probe/exec-liveness.yaml" >}}
+{{% code file="pods/probe/exec-liveness.yaml" %}}
 
 <!--
 In the configuration file, you can see that the Pod has a single `Container`.
@@ -229,7 +229,7 @@ file for a Pod that runs a container based on the `registry.k8s.io/liveness` ima
 另外一种类型的存活探测方式是使用 HTTP GET 请求。
 下面是一个 Pod 的配置文件，其中运行一个基于 `registry.k8s.io/liveness` 镜像的容器。
 
-{{< codenew file="pods/probe/http-liveness.yaml" >}}
+{{% code file="pods/probe/http-liveness.yaml" %}}
 
 <!--
 In the configuration file, you can see that the Pod has a single container.
@@ -325,7 +325,7 @@ can't it is considered a failure.
 使用这种配置时，kubelet 会尝试在指定端口和容器建立套接字链接。
 如果能建立连接，这个容器就被看作是健康的，如果不能则这个容器就被看作是有问题的。
 
-{{< codenew file="pods/probe/tcp-liveness-readiness.yaml" >}}
+{{% code file="pods/probe/tcp-liveness-readiness.yaml" %}}
 
 <!--
 As you can see, configuration for a TCP check is quite similar to an HTTP check.
@@ -393,7 +393,7 @@ kubelet 可以配置为使用该协议来执行应用存活性检查。
 
 下面是一个示例清单：
 
-{{< codenew file="pods/probe/grpc-liveness.yaml" >}}
+{{% code file="pods/probe/grpc-liveness.yaml" %}}
 
 <!--
 To use a gRPC probe, `port` must be configured. If you want to distinguish probes of different types

content/zh-cn/docs/tasks/configure-pod-container/configure-pod-initialization.md

@@ -38,7 +38,7 @@ Here is the configuration file for the Pod:
 
 下面是 Pod 的配置文件：
 
-{{< codenew file="pods/init-containers.yaml" >}}
+{{% code file="pods/init-containers.yaml" %}}
 
 <!--
 In the configuration file, you can see that the Pod has a Volume that the init