whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync from EN verison, move Pod Overhead concept inside Scheduling & Eviction

Browse Source
This commit is contained in:
yuanhao
2020-11-10 09:56:00 +08:00
parent e3109f5829
commit 0871ec8196
1 changed files with 306 additions and 306 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/zh/docs/concepts/configuration/pod-overhead.md → content/zh/docs/concepts/scheduling-eviction/pod-overhead.md
+3 -3
View File
@@ -118,7 +118,7 @@ spec:
``` ```
<!-- <!--
At admission time the RuntimeClass [admission controller](https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/) At admission time the RuntimeClass [admission controller](/docs/reference/access-authn-authz/admission-controllers/)
updates the workload's PodSpec to include the `overhead` as described in the RuntimeClass. If the PodSpec already has this field defined, updates the workload's PodSpec to include the `overhead` as described in the RuntimeClass. If the PodSpec already has this field defined,
the Pod will be rejected. In the given example, since only the RuntimeClass name is specified, the admission controller mutates the Pod the Pod will be rejected. In the given example, since only the RuntimeClass name is specified, the admission controller mutates the Pod
to include an `overhead`. to include an `overhead`.
@@ -222,12 +222,12 @@ is used on the node, which provides a CLI for CRI-compatible container runtimes.
advanced example to show PodOverhead behavior, and it is not expected that users should need to check advanced example to show PodOverhead behavior, and it is not expected that users should need to check
cgroups directly on the node. cgroups directly on the node.
First, on the particular node, determine the Pod identifier:ying First, on the particular node, determine the Pod identifier:
--> -->
在工作负载所运行的节点上检查 Pod 的内存 cgroups. 在接下来的例子中，将在该节点上使用具备 CRI 兼容的容器运行时命令行工具 [`crictl`](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md). 在工作负载所运行的节点上检查 Pod 的内存 cgroups. 在接下来的例子中，将在该节点上使用具备 CRI 兼容的容器运行时命令行工具 [`crictl`](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md).
这是一个展示 PodOverhead 行为的进阶示例，用户并不需要直接在该节点上检查 cgroups. 这是一个展示 PodOverhead 行为的进阶示例，用户并不需要直接在该节点上检查 cgroups.
首先在特定的节点上确定该 Pod 的标识符：ying 首先在特定的节点上确定该 Pod 的标识符：
<!-- <!--
```bash ```bash