File tree Expand file tree Collapse file tree 1 file changed +2
-2
lines changed
content/en/docs/concepts/containers Expand file tree Collapse file tree 1 file changed +2
-2
lines changed Original file line number Diff line number Diff line change @@ -51,7 +51,7 @@ CRI implementation for how to configure.
51
51
{{< note >}}
52
52
RuntimeClass assumes a homogeneous node configuration across the cluster by default (which means
53
53
that all nodes are configured the same way with respect to container runtimes). To support
54
- heterogenous node configurations, see [ Scheduling] ( #scheduling ) below.
54
+ heterogeneous node configurations, see [ Scheduling] ( #scheduling ) below.
55
55
{{< /note >}}
56
56
57
57
The configurations have a corresponding ` handler ` name, referenced by the RuntimeClass. The
@@ -144,7 +144,7 @@ See CRI-O's [config documentation](https://raw.githubusercontent.com/cri-o/cri-o
144
144
145
145
{{< feature-state for_k8s_version="v1.16" state="beta" >}}
146
146
147
- As of Kubernetes v1.16, RuntimeClass includes support for heterogenous clusters through its
147
+ As of Kubernetes v1.16, RuntimeClass includes support for heterogeneous clusters through its
148
148
`scheduling` fields. Through the use of these fields, you can ensure that pods running with this
149
149
RuntimeClass are scheduled to nodes that support it. To use the scheduling support, you must have
150
150
the [RuntimeClass admission controller](/docs/reference/access-authn-authz/admission-controllers/#runtimeclass)
You can’t perform that action at this time.
0 commit comments