Skip to content

Commit 19085a3

Browse files
committed
[zh] Resync page quality-service-pod
1 parent bfd636a commit 19085a3

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ kubectl create namespace qos-example
6262
<!--
6363
## Create a Pod that gets assigned a QoS class of Guaranteed
6464
65-
For a Pod to be given a QoS class of Guaranteed:
65+
For a Pod to be given a QoS class of `Guaranteed`:
6666
6767
* Every Container in the Pod must have a memory limit and a memory request.
6868
* For every Container in the Pod, the memory limit must equal the memory request.
@@ -72,7 +72,7 @@ For a Pod to be given a QoS class of Guaranteed:
7272
-->
7373
## 创建一个 QoS 类为 Guaranteed 的 Pod {#create-a-pod-that-gets-assigned-a-qos-class-of-guaranteed}
7474

75-
对于 QoS 类为 Guaranteed 的 Pod:
75+
对于 QoS 类为 `Guaranteed` 的 Pod:
7676

7777
* Pod 中的每个容器都必须指定内存限制和内存请求。
7878
* 对于 Pod 中的每个容器,内存限制必须等于内存请求。
@@ -116,11 +116,11 @@ kubectl get pod qos-demo --namespace=qos-example --output=yaml
116116
```
117117

118118
<!--
119-
The output shows that Kubernetes gave the Pod a QoS class of Guaranteed. The output also
119+
The output shows that Kubernetes gave the Pod a QoS class of `Guaranteed`. The output also
120120
verifies that the Pod Container has a memory request that matches its memory limit, and it has
121121
a CPU request that matches its CPU limit.
122122
-->
123-
结果表明 Kubernetes 为 Pod 配置的 QoS 类为 Guaranteed。
123+
结果表明 Kubernetes 为 Pod 配置的 QoS 类为 `Guaranteed`
124124
结果也确认了 Pod 容器设置了与内存限制匹配的内存请求,设置了与 CPU 限制匹配的 CPU 请求。
125125

126126
```yaml
@@ -247,7 +247,7 @@ kubectl delete pod qos-demo-2 --namespace=qos-example
247247
For a Pod to be given a QoS class of `BestEffort`, the Containers in the Pod must not
248248
have any memory or CPU limits or requests.
249249
250-
Here is the configuration file for a Pod that has one Container. The Container has no memory or CPU
250+
Here is a manifest for a Pod that has one Container. The Container has no memory or CPU
251251
limits or requests:
252252
-->
253253
## 创建一个 QoS 类为 BestEffort 的 Pod {#create-a-pod-that-gets-assigned-a-qos-class-of-besteffort}
@@ -308,23 +308,23 @@ kubectl delete pod qos-demo-3 --namespace=qos-example
308308
<!--
309309
## Create a Pod that has two Containers
310310
311-
Here is the configuration file for a Pod that has two Containers. One container specifies a memory
311+
Here is a manifest for a Pod that has two Containers. One container specifies a memory
312312
request of 200 MiB. The other Container does not specify any requests or limits.
313313
-->
314314
## 创建包含两个容器的 Pod {#create-a-pod-that-has-two-containers}
315315

316-
下面是包含两个 Container 的 Pod 配置文件。一个 Container 指定内存请求为 200 MiB。
316+
下面是包含两个 Container 的 Pod 清单。一个 Container 指定内存请求为 200 MiB。
317317
另外一个 Container 没有指定任何请求或限制。
318318

319319
{{< codenew file="pods/qos/qos-pod-4.yaml" >}}
320320

321321
<!--
322322
Notice that this Pod meets the criteria for QoS class `Burstable`. That is, it does not meet the
323-
criteria for QoS class Guaranteed, and one of its Containers has a memory request.
323+
criteria for QoS class `Guaranteed`, and one of its Containers has a memory request.
324324
325325
Create the Pod:
326326
-->
327-
注意此 Pod 满足 `Burstable` QoS 类的标准。也就是说它不满足 Guaranteed QoS 类标准,
327+
注意此 Pod 满足 `Burstable` QoS 类的标准。也就是说它不满足 `Guaranteed` QoS 类标准,
328328
因为它的 Container 之一设有内存请求。
329329

330330
创建 Pod:

0 commit comments

Comments
 (0)