@@ -113,7 +113,7 @@ Deployment 管理一个 [ReplicaSet](/zh-cn/docs/concepts/workloads/controllers/
113
113
ReplicaSet 再管理 Pod,从而使调度器能够免受一些故障的影响。
114
114
以下是 Deployment 配置,将其保存为 ` my-scheduler.yaml ` :
115
115
116
- {{< codenew file="admin/sched/my-scheduler.yaml" > }}
116
+ {{% code file="admin/sched/my-scheduler.yaml" % }}
117
117
118
118
<!--
119
119
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`
236
236
kubectl edit clusterrole system:kube-scheduler
237
237
```
238
238
239
- {{< codenew file="admin/sched/clusterrole.yaml" > }}
239
+ {{% code file="admin/sched/clusterrole.yaml" % }}
240
240
241
241
<!--
242
242
## Specify schedulers for pods
@@ -257,7 +257,7 @@ scheduler in that pod spec. Let's look at three examples.
257
257
-->
258
258
- Pod spec 没有任何调度器名称
259
259
260
- {{< codenew file="admin/sched/pod1.yaml" > }}
260
+ {{% code file="admin/sched/pod1.yaml" % }}
261
261
262
262
<!--
263
263
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.
279
279
-->
280
280
- Pod spec 设置为 ` default-scheduler `
281
281
282
- {{< codenew file="admin/sched/pod2.yaml" > }}
282
+ {{% code file="admin/sched/pod2.yaml" % }}
283
283
284
284
<!--
285
285
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.
302
302
-->
303
303
- Pod spec 设置为 ` my-scheduler `
304
304
305
- {{< codenew file="admin/sched/pod3.yaml" > }}
305
+ {{% code file="admin/sched/pod3.yaml" % }}
306
306
307
307
<!--
308
308
In this case, we specify that this pod should be scheduled using the scheduler that we
0 commit comments