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

restore not-outdated contents

Browse Source
This commit is contained in:
Naoki Oketani
2021-01-04 14:03:52 +09:00
parent 3b409773ae
commit 9315b85fd7
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/containers/runtime-class.md
+5 -3
View File
@@ -140,9 +140,9 @@ See CRI-O's [config documentation](https://raw.githubusercontent.com/cri-o/cri-o
{{< feature-state for_k8s_version="v1.16" state="beta" >}} {{< feature-state for_k8s_version="v1.16" state="beta" >}}
If the nodes in your cluster support different sets of features, you can set the `scheduling` By specifying the `scheduling` field for a RuntimeClass, you can set constraints to
field for a RuntimeClass, then use that hint to ensure that pods running with that particular ensure that Pods running with this RuntimeClass are scheduled to nodes that support it.
RuntimeClass are scheduled to nodes that support it. If `scheduling` is not set, this RuntimeClass is assumed to be supported by all nodes.
To ensure pods land on nodes supporting a specific RuntimeClass, that set of nodes should have a To ensure pods land on nodes supporting a specific RuntimeClass, that set of nodes should have a
common label which is then selected by the `runtimeclass.scheduling.nodeSelector` field. The common label which is then selected by the `runtimeclass.scheduling.nodeSelector` field. The
@@ -164,6 +164,8 @@ Nodes](/docs/concepts/scheduling-eviction/assign-pod-node/).
You can specify _overhead_ resources that are associated with running a Pod. Declaring overhead allows You can specify _overhead_ resources that are associated with running a Pod. Declaring overhead allows
the cluster (including the scheduler) to account for it when making decisions about Pods and resources. the cluster (including the scheduler) to account for it when making decisions about Pods and resources.
To use Pod overhead, you must have the PodOverhead [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
enabled (it is on by default).
Pod overhead is defined in RuntimeClass through the `overhead` fields. Through the use of these fields, Pod overhead is defined in RuntimeClass through the `overhead` fields. Through the use of these fields,
you can specify the overhead of running pods utilizing this RuntimeClass and ensure these overheads you can specify the overhead of running pods utilizing this RuntimeClass and ensure these overheads