Merge pull request #42536 from asa3311/sync-zh-49

[zh] sync communicate-containers-same-pod-shared-volume configure-multiple-schedulers managing-tls-in-a-cluster

content/zh-cn/docs/tasks/access-application-cluster/communicate-containers-same-pod-shared-volume.md

@@ -38,7 +38,7 @@ for the Pod:
 在这个练习中，你会创建一个包含两个容器的 Pod。两个容器共享一个卷用于他们之间的通信。
 Pod 的配置文件如下：
 
-{{< codenew file="pods/two-container-pod.yaml" >}}
+{{% code file="pods/two-container-pod.yaml" %}}
 
 <!--
 In the configuration file, you can see that the Pod has a Volume named

content/zh-cn/docs/tasks/extend-kubernetes/configure-multiple-schedulers.md

@@ -113,7 +113,7 @@ Deployment 管理一个 [ReplicaSet](/zh-cn/docs/concepts/workloads/controllers/
 ReplicaSet 再管理 Pod，从而使调度器能够免受一些故障的影响。
 以下是 Deployment 配置，将其保存为 `my-scheduler.yaml`：
 
-{{< codenew file="admin/sched/my-scheduler.yaml" >}}
+{{% code file="admin/sched/my-scheduler.yaml" %}}
 
 <!--
 In the above manifest, you use a [KubeSchedulerConfiguration](/docs/reference/scheduling/config/)
@@ -236,7 +236,7 @@ Add your scheduler name to the resourceNames of the rule applied for `endpoints`
 kubectl edit clusterrole system:kube-scheduler
 ```
 
-{{< codenew file="admin/sched/clusterrole.yaml" >}}
+{{% code file="admin/sched/clusterrole.yaml" %}}
 
 <!--
 ## Specify schedulers for pods
@@ -257,7 +257,7 @@ scheduler in that pod spec. Let's look at three examples.
 -->
 - Pod spec 没有任何调度器名称
 
-  {{< codenew file="admin/sched/pod1.yaml" >}}
+  {{% code file="admin/sched/pod1.yaml" %}}
 
   <!--
   When no scheduler name is supplied, the pod is automatically scheduled using the
@@ -279,7 +279,7 @@ scheduler in that pod spec. Let's look at three examples.
 -->
 - Pod spec 设置为 `default-scheduler`
 
-  {{< codenew file="admin/sched/pod2.yaml" >}}
+  {{% code file="admin/sched/pod2.yaml" %}}
 
   <!--
   A scheduler is specified by supplying the scheduler name as a value to `spec.schedulerName`. In this case, we supply the name of the
@@ -302,7 +302,7 @@ scheduler in that pod spec. Let's look at three examples.
 -->
 - Pod spec 设置为 `my-scheduler`
 
-  {{< codenew file="admin/sched/pod3.yaml" >}}
+  {{% code file="admin/sched/pod3.yaml" %}}
 
   <!--
   In this case, we specify that this pod should be scheduled using the scheduler that we

content/zh-cn/docs/tasks/tls/managing-tls-in-a-cluster.md

@@ -346,7 +346,7 @@ This produces a certificate authority key file (`ca-key.pem`) and certificate (`
 <!-- ### Issue a certificate -->
 ### 颁发证书
 
-{{< codenew file="tls/server-signing-config.json" >}}
+{{% code file="tls/server-signing-config.json" %}}
 
 <!-- 
 Use a `server-signing-config.json` signing configuration and the certificate authority key file