Skip to content

Commit 6d3066f

Browse files
authored
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
2 parents ab1f44a + d65b530 commit 6d3066f

File tree

3 files changed

+7
-7
lines changed

3 files changed

+7
-7
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ for the Pod:
3838
在这个练习中,你会创建一个包含两个容器的 Pod。两个容器共享一个卷用于他们之间的通信。
3939
Pod 的配置文件如下:
4040

41-
{{< codenew file="pods/two-container-pod.yaml" >}}
41+
{{% code file="pods/two-container-pod.yaml" %}}
4242

4343
<!--
4444
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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ Deployment 管理一个 [ReplicaSet](/zh-cn/docs/concepts/workloads/controllers/
113113
ReplicaSet 再管理 Pod,从而使调度器能够免受一些故障的影响。
114114
以下是 Deployment 配置,将其保存为 `my-scheduler.yaml`
115115

116-
{{< codenew file="admin/sched/my-scheduler.yaml" >}}
116+
{{% code file="admin/sched/my-scheduler.yaml" %}}
117117

118118
<!--
119119
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`
236236
kubectl edit clusterrole system:kube-scheduler
237237
```
238238

239-
{{< codenew file="admin/sched/clusterrole.yaml" >}}
239+
{{% code file="admin/sched/clusterrole.yaml" %}}
240240

241241
<!--
242242
## Specify schedulers for pods
@@ -257,7 +257,7 @@ scheduler in that pod spec. Let's look at three examples.
257257
-->
258258
- Pod spec 没有任何调度器名称
259259

260-
{{< codenew file="admin/sched/pod1.yaml" >}}
260+
{{% code file="admin/sched/pod1.yaml" %}}
261261

262262
<!--
263263
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.
279279
-->
280280
- Pod spec 设置为 `default-scheduler`
281281

282-
{{< codenew file="admin/sched/pod2.yaml" >}}
282+
{{% code file="admin/sched/pod2.yaml" %}}
283283

284284
<!--
285285
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.
302302
-->
303303
- Pod spec 设置为 `my-scheduler`
304304

305-
{{< codenew file="admin/sched/pod3.yaml" >}}
305+
{{% code file="admin/sched/pod3.yaml" %}}
306306

307307
<!--
308308
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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -346,7 +346,7 @@ This produces a certificate authority key file (`ca-key.pem`) and certificate (`
346346
<!-- ### Issue a certificate -->
347347
### 颁发证书
348348

349-
{{< codenew file="tls/server-signing-config.json" >}}
349+
{{% code file="tls/server-signing-config.json" %}}
350350

351351
<!--
352352
Use a `server-signing-config.json` signing configuration and the certificate authority key file

0 commit comments

Comments
 (0)