Skip to content

Commit e8b136c

Browse files
author
Mengjiao Liu
committed
Use code_sample shortcode instead of code shortcode
1 parent 234458f commit e8b136c

File tree

110 files changed

+280
-280
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

110 files changed

+280
-280
lines changed

‎content/en/docs/concepts/cluster-administration/flow-control.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -470,7 +470,7 @@ traffic, you can configure rules to block any health check requests
470470
that originate from outside your cluster.
471471
{{< /caution >}}
472472

473-
{{% code file="priority-and-fairness/health-for-strangers.yaml" %}}
473+
{{% code_sample file="priority-and-fairness/health-for-strangers.yaml" %}}
474474

475475
## Diagnostics
476476

@@ -885,7 +885,7 @@ from other requests.
885885

886886
Example FlowSchema object to isolate list event requests:
887887

888-
{{% code file="priority-and-fairness/list-events-default-service-account.yaml" %}}
888+
{{% code_sample file="priority-and-fairness/list-events-default-service-account.yaml" %}}
889889

890890
- This FlowSchema captures all list event calls made by the default service
891891
account in the default namespace. The matching precedence 8000 is lower than the

‎content/en/docs/concepts/cluster-administration/logging.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Kubernetes captures logs from each container in a running Pod.
3939
This example uses a manifest for a `Pod` with a container
4040
that writes text to the standard output stream, once per second.
4141

42-
{{% code file="debug/counter-pod.yaml" %}}
42+
{{% code_sample file="debug/counter-pod.yaml" %}}
4343

4444
To run this pod, use the following command:
4545

@@ -255,7 +255,7 @@ For example, a pod runs a single container, and the container
255255
writes to two different log files using two different formats. Here's a
256256
manifest for the Pod:
257257

258-
{{% code file="admin/logging/two-files-counter-pod.yaml" %}}
258+
{{% code_sample file="admin/logging/two-files-counter-pod.yaml" %}}
259259

260260
It is not recommended to write log entries with different formats to the same log
261261
stream, even if you managed to redirect both components to the `stdout` stream of
@@ -265,7 +265,7 @@ the logs to its own `stdout` stream.
265265

266266
Here's a manifest for a pod that has two sidecar containers:
267267

268-
{{% code file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" %}}
268+
{{% code_sample file="admin/logging/two-files-counter-pod-streaming-sidecar.yaml" %}}
269269

270270
Now when you run this pod, you can access each log stream separately by
271271
running the following commands:
@@ -332,7 +332,7 @@ Here are two example manifests that you can use to implement a sidecar container
332332
The first manifest contains a [`ConfigMap`](/docs/tasks/configure-pod-container/configure-pod-configmap/)
333333
to configure fluentd.
334334

335-
{{% code file="admin/logging/fluentd-sidecar-config.yaml" %}}
335+
{{% code_sample file="admin/logging/fluentd-sidecar-config.yaml" %}}
336336

337337
{{< note >}}
338338
In the sample configurations, you can replace fluentd with any logging agent, reading
@@ -342,7 +342,7 @@ from any source inside an application container.
342342
The second manifest describes a pod that has a sidecar container running fluentd.
343343
The pod mounts a volume where fluentd can pick up its configuration data.
344344

345-
{{% code file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" %}}
345+
{{% code_sample file="admin/logging/two-files-counter-pod-agent-sidecar.yaml" %}}
346346

347347
### Exposing logs directly from the application
348348

‎content/en/docs/concepts/cluster-administration/manage-deployment.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Many applications require multiple resources to be created, such as a Deployment
2222
Management of multiple resources can be simplified by grouping them together in the same file
2323
(separated by `---` in YAML). For example:
2424

25-
{{% code file="application/nginx-app.yaml" %}}
25+
{{% code_sample file="application/nginx-app.yaml" %}}
2626

2727
Multiple resources can be created the same way as a single resource:
2828

‎content/en/docs/concepts/configuration/configmap.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@ technique also lets you access a ConfigMap in a different namespace.
113113
114114
Here's an example Pod that uses values from `game-demo` to configure a Pod:
115115

116-
{{% code file="configmap/configure-pod.yaml" %}}
116+
{{% code_sample file="configmap/configure-pod.yaml" %}}
117117

118118
A ConfigMap doesn't differentiate between single line property values and
119119
multi-line file-like values.

‎content/en/docs/concepts/overview/working-with-objects/_index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ request.
7777

7878
Here's an example `.yaml` file that shows the required fields and object spec for a Kubernetes Deployment:
7979

80-
{{% code file="application/deployment.yaml" %}}
80+
{{% code_sample file="application/deployment.yaml" %}}
8181

8282
One way to create a Deployment using a `.yaml` file like the one above is to use the
8383
[`kubectl apply`](/docs/reference/generated/kubectl/kubectl-commands#apply) command

‎content/en/docs/concepts/policy/limit-range.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,12 +54,12 @@ A `LimitRange` does **not** check the consistency of the default values it appli
5454

5555
For example, you define a `LimitRange` with this manifest:
5656

57-
{{% code file="concepts/policy/limit-range/problematic-limit-range.yaml" %}}
57+
{{% code_sample file="concepts/policy/limit-range/problematic-limit-range.yaml" %}}
5858

5959

6060
along with a Pod that declares a CPU resource request of `700m`, but not a limit:
6161

62-
{{% code file="concepts/policy/limit-range/example-conflict-with-limitrange-cpu.yaml" %}}
62+
{{% code_sample file="concepts/policy/limit-range/example-conflict-with-limitrange-cpu.yaml" %}}
6363

6464

6565
then that Pod will not be scheduled, failing with an error similar to:
@@ -69,7 +69,7 @@ Pod "example-conflict-with-limitrange-cpu" is invalid: spec.containers[0].resour
6969

7070
If you set both `request` and `limit`, then that new Pod will be scheduled successfully even with the same `LimitRange` in place:
7171

72-
{{% code file="concepts/policy/limit-range/example-no-conflict-with-limitrange-cpu.yaml" %}}
72+
{{% code_sample file="concepts/policy/limit-range/example-no-conflict-with-limitrange-cpu.yaml" %}}
7373

7474
## Example resource constraints
7575

‎content/en/docs/concepts/policy/resource-quotas.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -687,7 +687,7 @@ plugins:
687687

688688
Then, create a resource quota object in the `kube-system` namespace:
689689

690-
{{% code file="policy/priority-class-resourcequota.yaml" %}}
690+
{{% code_sample file="policy/priority-class-resourcequota.yaml" %}}
691691

692692
```shell
693693
kubectl apply -f https://k8s.io/examples/policy/priority-class-resourcequota.yaml -n kube-system

‎content/en/docs/concepts/scheduling-eviction/assign-pod-node.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ your Pod spec.
121121

122122
For example, consider the following Pod spec:
123123

124-
{{% code file="pods/pod-with-node-affinity.yaml" %}}
124+
{{% code_sample file="pods/pod-with-node-affinity.yaml" %}}
125125

126126
In this example, the following rules apply:
127127

@@ -171,7 +171,7 @@ scheduling decision for the Pod.
171171

172172
For example, consider the following Pod spec:
173173

174-
{{% code file="pods/pod-with-affinity-anti-affinity.yaml" %}}
174+
{{% code_sample file="pods/pod-with-affinity-anti-affinity.yaml" %}}
175175

176176
If there are two possible nodes that match the
177177
`preferredDuringSchedulingIgnoredDuringExecution` rule, one with the
@@ -287,7 +287,7 @@ spec.
287287

288288
Consider the following Pod spec:
289289

290-
{{% code file="pods/pod-with-pod-affinity.yaml" %}}
290+
{{% code_sample file="pods/pod-with-pod-affinity.yaml" %}}
291291

292292
This example defines one Pod affinity rule and one Pod anti-affinity rule. The
293293
Pod affinity rule uses the "hard"

‎content/en/docs/concepts/scheduling-eviction/pod-scheduling-readiness.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ each schedulingGate can be removed in arbitrary order, but addition of a new sch
3131

3232
To mark a Pod not-ready for scheduling, you can create it with one or more scheduling gates like this:
3333

34-
{{% code file="pods/pod-with-scheduling-gates.yaml" %}}
34+
{{% code_sample file="pods/pod-with-scheduling-gates.yaml" %}}
3535

3636
After the Pod's creation, you can check its state using:
3737

@@ -61,7 +61,7 @@ The output is:
6161
To inform scheduler this Pod is ready for scheduling, you can remove its `schedulingGates` entirely
6262
by re-applying a modified manifest:
6363

64-
{{% code file="pods/pod-without-scheduling-gates.yaml" %}}
64+
{{% code_sample file="pods/pod-without-scheduling-gates.yaml" %}}
6565

6666
You can check if the `schedulingGates` is cleared by running:
6767

‎content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ tolerations:
6464
6565
Here's an example of a pod that uses tolerations:
6666
67-
{{% code file="pods/pod-with-toleration.yaml" %}}
67+
{{% code_sample file="pods/pod-with-toleration.yaml" %}}
6868
6969
The default value for `operator` is `Equal`.
7070

0 commit comments

Comments
 (0)