Merge pull request #42473 from asa3311/sync-zh-45

[zh] sync quality-service-pod resize-container-resources update-api-object-kubectl-patch
pull/42479/head
Kubernetes Prow Robot 2023-08-09 17:29:31 -07:00 committed by GitHub
commit 153531725c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 8 additions and 8 deletions

View File

@ -95,7 +95,7 @@ memory request, both equal to 200 MiB. The Container has a CPU limit and a CPU r
下面是包含一个 Container 的 Pod 清单。该 Container 设置了内存请求和内存限制,值都是 200 MiB。
该 Container 设置了 CPU 请求和 CPU 限制,值都是 700 milliCPU
{{< codenew file="pods/qos/qos-pod.yaml" >}}
{{% code file="pods/qos/qos-pod.yaml" %}}
<!--
Create the Pod:
@ -186,7 +186,7 @@ and a memory request of 100 MiB.
下面是包含一个 Container 的 Pod 清单。该 Container 设置的内存限制为 200 MiB
内存请求为 100 MiB。
{{< codenew file="pods/qos/qos-pod-2.yaml" >}}
{{% code file="pods/qos/qos-pod-2.yaml" %}}
<!--
Create the Pod:
@ -256,7 +256,7 @@ limits or requests:
下面是包含一个 Container 的 Pod 清单。该 Container 没有设置内存和 CPU 限制或请求。
{{< codenew file="pods/qos/qos-pod-3.yaml" >}}
{{% code file="pods/qos/qos-pod-3.yaml" %}}
<!--
Create the Pod:
@ -316,7 +316,7 @@ request of 200 MiB. The other Container does not specify any requests or limits.
下面是包含两个 Container 的 Pod 清单。一个 Container 指定内存请求为 200 MiB。
另外一个 Container 没有指定任何请求或限制。
{{< codenew file="pods/qos/qos-pod-4.yaml" >}}
{{% code file="pods/qos/qos-pod-4.yaml" %}}
<!--
Notice that this Pod meets the criteria for QoS class `Burstable`. That is, it does not meet the

View File

@ -166,7 +166,7 @@ Consider the following manifest for a Pod that has one Container.
考虑以下包含一个容器的 Pod 的清单。
{{< codenew file="pods/qos/qos-pod-5.yaml" >}}
{{% code file="pods/qos/qos-pod-5.yaml" %}}
<!--
Create the pod in the `qos-example` namespace:

View File

@ -37,7 +37,7 @@ is a Pod that has one container:
下面是具有两个副本的 Deployment 的配置文件。每个副本是一个 Pod有一个容器
{{% codenew file="application/deployment-patch.yaml" %}}
{{% code file="application/deployment-patch.yaml" %}}
<!--
Create the Deployment:
@ -418,7 +418,7 @@ Here's the configuration file for a Deployment that uses the `RollingUpdate` str
-->
## 使用带 retainKeys 策略的策略合并 patch 更新 Deployment {#use-strategic-merge-patch-to-update-a-deployment-using-the-retainkeys-strategy}
{{% codenew file="application/deployment-retainkeys.yaml" %}}
{{% code file="application/deployment-retainkeys.yaml" %}}
<!--
Create the deployment:
@ -651,7 +651,7 @@ Deployment 是支持这些子资源的其中一个例子。
下面是有两个副本的 Deployment 的清单。
{{% codenew file="application/deployment.yaml" %}}
{{% code file="application/deployment.yaml" %}}
<!--
Create the Deployment: