[zh] Resync tasks pages (task-3)
This commit is contained in:
Qiming Teng
+5
-3
@@ -150,11 +150,11 @@ on these resources, the two values must be the same.
|
||||
<!--
|
||||
Here's a manifest for a Pod that has one container. The container manifest
|
||||
specifies a CPU request of 500 millicpu and a CPU limit of 800 millicpu. These satisfy the
|
||||
minimum and maximum CPU constraints imposed by the LimitRange.
|
||||
minimum and maximum CPU constraints imposed by the LimitRange for this namespace.
|
||||
-->
|
||||
以下为某个仅包含一个容器的 Pod 的清单。
|
||||
该容器声明了 CPU 请求 500 millicpu 和 CPU 限制 800 millicpu 。
|
||||
这些参数满足了 LimitRange 对象规定的 CPU 最小和最大限制。
|
||||
这些参数满足了 LimitRange 对象为此名字空间规定的 CPU 最小和最大限制。
|
||||
|
||||
{{< codenew file="admin/resource/cpu-constraints-pod.yaml" >}}
|
||||
|
||||
@@ -336,7 +336,7 @@ from the LimitRange for this namespace.
|
||||
设置[默认的 CPU 请求和限制](/zh/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/)。
|
||||
|
||||
<!--
|
||||
At this point, your Pod might be running or it might not be running. Recall that a prerequisite for
|
||||
At this point, your Pod may or may not be running. Recall that a prerequisite for
|
||||
this task is that your Nodes must have at least 1 CPU available for use. If each of your Nodes has only 1 CPU,
|
||||
then there might not be enough allocatable CPU on any Node to accommodate a request of 800 millicpu.
|
||||
If you happen to be using Nodes with 2 CPU, then you probably have enough CPU to accommodate the 800 millicpu request.
|
||||
@@ -348,6 +348,8 @@ Delete your Pod:
|
||||
如果你的每个节点都只有 1 CPU，那将没有一个节点拥有足够的可分配 CPU 来满足 800 millicpu 的请求。
|
||||
如果你在用的节点恰好有 2 CPU，那么有可能有足够的 CPU 来满足 800 millicpu 的请求。
|
||||
|
||||
删除你的 Pod：
|
||||
|
||||
```
|
||||
kubectl delete pod constraints-cpu-demo-4 --namespace=constraints-cpu-example
|
||||
```
|
||||
|
||||
+3
-2
@@ -213,9 +213,10 @@ kubectl apply -f https://k8s.io/examples/admin/resource/cpu-defaults-pod-3.yaml
|
||||
```
|
||||
|
||||
<!--
|
||||
View the specification of the Pod that you created:
|
||||
View the [specification](/docs/concepts/overview/working-with-objects/kubernetes-objects/#object-spec-and-status)
|
||||
of the Pod that you created:
|
||||
-->
|
||||
查看所你创建的 Pod 的规约:
|
||||
查看你所创建的 Pod 的[规约](/zh/docs/concepts/overview/working-with-objects/kubernetes-objects/#object-spec-and-status)：
|
||||
|
||||
```
|
||||
kubectl get pod default-cpu-demo-3 --output=yaml --namespace=default-cpu-example
|
||||
|
||||
+11
-10
@@ -3,7 +3,8 @@ title: 配置命名空间的最小和最大内存约束
|
||||
content_type: task
|
||||
weight: 30
|
||||
description: >-
|
||||
为命名口空间定义一个有效的内存资源限制范围，在该命名空间中每个新创建 Pod 的内存资源是在设置的范围内。
|
||||
为命名口空间定义一个有效的内存资源限制范围，在该命名空间中每个新创建
|
||||
Pod 的内存资源是在设置的范围内。
|
||||
---
|
||||
|
||||
<!--
|
||||
@@ -16,14 +17,17 @@ weight: 30
|
||||
|
||||
<!--
|
||||
This page shows how to set minimum and maximum values for memory used by containers
|
||||
running in a namespace. You specify minimum and maximum memory values in a
|
||||
[LimitRange](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#limitrange-v1-core)
|
||||
running in a {{< glossary_tooltip text="namespace" term_id="namespace" >}}.
|
||||
You specify minimum and maximum memory values in a
|
||||
[LimitRange](/docs/reference/kubernetes-api/policy-resources/limit-range-v1/)
|
||||
object. If a Pod does not meet the constraints imposed by the LimitRange,
|
||||
it cannot be created in the namespace.
|
||||
-->
|
||||
本页介绍如何设置在命名空间中运行的容器使用的内存的最小值和最大值。 你可以在
|
||||
[LimitRange](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#limitrange-v1-core)
|
||||
对象中指定最小和最大内存值。如果 Pod 不满足 LimitRange 施加的约束，则无法在命名空间中创建它。
|
||||
本页介绍如何设置在{{< glossary_tooltip text="名字空间" term_id="namespace" >}}
|
||||
中运行的容器所使用的内存的最小值和最大值。你可以在
|
||||
[LimitRange](/docs/reference/kubernetes-api/policy-resources/limit-range-v1/)
|
||||
对象中指定最小和最大内存值。如果 Pod 不满足 LimitRange 施加的约束，
|
||||
则无法在名字空间中创建它。
|
||||
|
||||
## {{% heading "prerequisites" %}}
|
||||
|
||||
@@ -32,7 +36,6 @@ it cannot be created in the namespace.
|
||||
<!--
|
||||
You must have access to create namespaces in your cluster.
|
||||
Each node in your cluster must have at least 1 GiB of memory available for Pods.
|
||||
|
||||
-->
|
||||
在你的集群里你必须要有创建命名空间的权限。
|
||||
|
||||
@@ -108,7 +111,7 @@ Now whenever you define a Pod within the constraints-mem-example namespace, Kube
|
||||
performs these steps:
|
||||
|
||||
* If any container in that Pod does not specify its own memory request and limit,
|
||||
the control plane assig nthe default memory request and limit to that container.
|
||||
the control plane assigns the default memory request and limit to that container.
|
||||
|
||||
* Verify that every container in that Pod requests at least 500 MiB of memory.
|
||||
|
||||
@@ -122,9 +125,7 @@ minimum and maximum memory constraints imposed by the LimitRange.
|
||||
现在，每当在 constraints-mem-example 命名空间中创建 Pod 时，Kubernetes 就会执行下面的步骤：
|
||||
|
||||
* 如果 Pod 中的任何容器未声明自己的内存请求和限制，控制面将为该容器设置默认的内存请求和限制。
|
||||
|
||||
* 确保该 Pod 中的每个容器的内存请求至少 500 MiB。
|
||||
|
||||
* 确保该 Pod 中每个容器内存请求不大于 1 GiB。
|
||||
|
||||
以下为包含一个容器的 Pod 清单。该容器声明了 600 MiB 的内存请求和 800 MiB 的内存限制，
|
||||
|
||||
+2
-2
@@ -3,7 +3,7 @@ title: 为命名空间配置默认的内存请求和限制
|
||||
content_type: task
|
||||
weight: 10
|
||||
description: >-
|
||||
为命名空间定义默认的内存资源限制，在该命名空间中每个新建的 Pod 都会被配置上内存资源限制。
|
||||
为命名空间定义默认的内存资源限制，这样在该命名空间中每个新建的 Pod 都会被配置上内存资源限制。
|
||||
---
|
||||
|
||||
<!--
|
||||
@@ -113,7 +113,7 @@ does not specify a memory request and limit.
|
||||
<!--
|
||||
Create the Pod.
|
||||
-->
|
||||
创建 Pod
|
||||
创建 Pod：
|
||||
|
||||
```shell
|
||||
kubectl apply -f https://k8s.io/examples/admin/resource/memory-defaults-pod.yaml --namespace=default-mem-example
|
||||
|
||||
Reference in New Issue
Block a user