diff --git a/static/docs/reference/generated/kubernetes-api/v1.19/index.html b/static/docs/reference/generated/kubernetes-api/v1.19/index.html index 1f88835146..71160a9eaa 100644 --- a/static/docs/reference/generated/kubernetes-api/v1.19/index.html +++ b/static/docs/reference/generated/kubernetes-api/v1.19/index.html @@ -8196,7 +8196,7 @@ spec: <TR><TD><CODE>initContainers</CODE><BR /><I><a href="#container-v1-core">Container</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, Liveness probes, or Startup probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/</TD></TR> <TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.</TD></TR> <TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node's labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/</TD></TR> -<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.16, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.16, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>preemptionPolicy</CODE><BR /><I>string</I></TD><TD>PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset. This field is beta-level, gated by the NonPreemptingPriority feature-gate.</TD></TR> <TR><TD><CODE>priority</CODE><BR /><I>integer</I></TD><TD>The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.</TD></TR> <TR><TD><CODE>priorityClassName</CODE><BR /><I>string</I></TD><TD>If specified, indicates the pod's priority. "system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.</TD></TR> @@ -28067,7 +28067,7 @@ $ curl -X GET 'http://127.0.0.1:8001/api/v1/watch/namespaces/default/services/de <TR><TD><CODE>handler</CODE><BR /><I>string</I></TD><TD>Handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration. It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called "runc" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR> <TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR> <TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR> -<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1beta1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1beta1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1beta1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR> </TBODY> </TABLE> @@ -47498,7 +47498,7 @@ The contents of the target Secret's Data field will be presented in a volume <TABLE> <THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD> <TBODY> -<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1alpha1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1alpha1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>runtimeHandler</CODE><BR /><I>string</I></TD><TD>RuntimeHandler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration. It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called "runc" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The RuntimeHandler must conform to the DNS Label (RFC 1123) requirements and is immutable.</TD></TR> <TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1alpha1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR> </TBODY> diff --git a/static/docs/reference/generated/kubernetes-api/v1.20/index.html b/static/docs/reference/generated/kubernetes-api/v1.20/index.html index 7476971f21..8f8d883eba 100644 --- a/static/docs/reference/generated/kubernetes-api/v1.20/index.html +++ b/static/docs/reference/generated/kubernetes-api/v1.20/index.html @@ -8368,7 +8368,7 @@ spec: <TR><TD><CODE>initContainers</CODE><BR /><I><a href="#container-v1-core">Container</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, Liveness probes, or Startup probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/</TD></TR> <TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.</TD></TR> <TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node's labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/</TD></TR> -<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.16, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.16, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>preemptionPolicy</CODE><BR /><I>string</I></TD><TD>PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset. This field is beta-level, gated by the NonPreemptingPriority feature-gate.</TD></TR> <TR><TD><CODE>priority</CODE><BR /><I>integer</I></TD><TD>The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.</TD></TR> <TR><TD><CODE>priorityClassName</CODE><BR /><I>string</I></TD><TD>If specified, indicates the pod's priority. "system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.</TD></TR> @@ -49107,7 +49107,7 @@ The contents of the target Secret's Data field will be presented in a volume <TR><TD><CODE>handler</CODE><BR /><I>string</I></TD><TD>Handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration. It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called "runc" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR> <TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR> <TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR> -<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1beta1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1beta1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1beta1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR> </TBODY> </TABLE> @@ -49444,7 +49444,7 @@ The contents of the target Secret's Data field will be presented in a volume <TABLE> <THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD> <TBODY> -<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1alpha1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1alpha1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>runtimeHandler</CODE><BR /><I>string</I></TD><TD>RuntimeHandler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration. It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called "runc" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The RuntimeHandler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR> <TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1alpha1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR> </TBODY> diff --git a/static/docs/reference/generated/kubernetes-api/v1.21/index.html b/static/docs/reference/generated/kubernetes-api/v1.21/index.html index b5e02991ad..adb84852b1 100644 --- a/static/docs/reference/generated/kubernetes-api/v1.21/index.html +++ b/static/docs/reference/generated/kubernetes-api/v1.21/index.html @@ -8409,7 +8409,7 @@ spec: <TR><TD><CODE>initContainers</CODE><BR /><I><a href="#container-v1-core">Container</a> array</I><BR /><B>patch strategy</B>: <I>merge</I><BR /><B>patch merge key</B>: <I>name</I></TD><TD>List of initialization containers belonging to the pod. Init containers are executed in order prior to containers being started. If any init container fails, the pod is considered to have failed and is handled according to its restartPolicy. The name for an init container or normal container must be unique among all containers. Init containers may not have Lifecycle actions, Readiness probes, Liveness probes, or Startup probes. The resourceRequirements of an init container are taken into account during scheduling by finding the highest request/limit for each resource type, and then using the max of of that value or the sum of the normal containers. Limits are applied to init containers in a similar fashion. Init containers cannot currently be added or removed. Cannot be updated. More info: https://kubernetes.io/docs/concepts/workloads/pods/init-containers/</TD></TR> <TR><TD><CODE>nodeName</CODE><BR /><I>string</I></TD><TD>NodeName is a request to schedule this pod onto a specific node. If it is non-empty, the scheduler simply schedules this pod onto that node, assuming that it fits resource requirements.</TD></TR> <TR><TD><CODE>nodeSelector</CODE><BR /><I>object</I></TD><TD>NodeSelector is a selector which must be true for the pod to fit on a node. Selector which must match a node's labels for the pod to be scheduled on that node. More info: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/</TD></TR> -<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.16, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I>object</I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. This field will be autopopulated at admission time by the RuntimeClass admission controller. If the RuntimeClass admission controller is enabled, overhead must not be set in Pod create requests. The RuntimeClass admission controller will reject Pod create requests which have the overhead already set. If RuntimeClass is configured and selected in the PodSpec, Overhead will be set to the value defined in the corresponding RuntimeClass, otherwise it will remain unset and treated as zero. More info: https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.16, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>preemptionPolicy</CODE><BR /><I>string</I></TD><TD>PreemptionPolicy is the Policy for preempting pods with lower priority. One of Never, PreemptLowerPriority. Defaults to PreemptLowerPriority if unset. This field is beta-level, gated by the NonPreemptingPriority feature-gate.</TD></TR> <TR><TD><CODE>priority</CODE><BR /><I>integer</I></TD><TD>The priority value. Various system components use this field to find the priority of the pod. When Priority Admission Controller is enabled, it prevents users from setting this field. The admission controller populates this field from PriorityClassName. The higher the value, the higher the priority.</TD></TR> <TR><TD><CODE>priorityClassName</CODE><BR /><I>string</I></TD><TD>If specified, indicates the pod's priority. "system-node-critical" and "system-cluster-critical" are two special keywords which indicate the highest priorities with the former being the highest priority. Any other name must be defined by creating a PriorityClass object with that name. If not specified, the pod priority will be default or zero if there is no default.</TD></TR> @@ -49976,7 +49976,7 @@ The contents of the target Secret's Data field will be presented in a volume <TR><TD><CODE>handler</CODE><BR /><I>string</I></TD><TD>Handler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration. It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called "runc" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The Handler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR> <TR><TD><CODE>kind</CODE><BR /><I>string</I></TD><TD>Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds</TD></TR> <TR><TD><CODE>metadata</CODE><BR /><I><a href="#objectmeta-v1-meta">ObjectMeta</a></I></TD><TD>More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata</TD></TR> -<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1beta1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1beta1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1beta1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR> </TBODY> </TABLE> @@ -50311,7 +50311,7 @@ The contents of the target Secret's Data field will be presented in a volume <TABLE> <THEAD><TR><TH>Field</TH><TH>Description</TH></TR></THEAD> <TBODY> -<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1alpha1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/20190226-pod-overhead.md This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> +<TR><TD><CODE>overhead</CODE><BR /><I><a href="#overhead-v1alpha1-node-k8s-io">Overhead</a></I></TD><TD>Overhead represents the resource overhead associated with running a pod for a given RuntimeClass. For more details, see https://git.k8s.io/enhancements/keps/sig-node/688-pod-overhead This field is alpha-level as of Kubernetes v1.15, and is only honored by servers that enable the PodOverhead feature.</TD></TR> <TR><TD><CODE>runtimeHandler</CODE><BR /><I>string</I></TD><TD>RuntimeHandler specifies the underlying runtime and configuration that the CRI implementation will use to handle pods of this class. The possible values are specific to the node & CRI configuration. It is assumed that all handlers are available on every node, and handlers of the same name are equivalent on every node. For example, a handler called "runc" might specify that the runc OCI runtime (using native Linux containers) will be used to run the containers in a pod. The RuntimeHandler must be lowercase, conform to the DNS Label (RFC 1123) requirements, and is immutable.</TD></TR> <TR><TD><CODE>scheduling</CODE><BR /><I><a href="#scheduling-v1alpha1-node-k8s-io">Scheduling</a></I></TD><TD>Scheduling holds the scheduling constraints to ensure that pods running with this RuntimeClass are scheduled to nodes that support it. If scheduling is nil, this RuntimeClass is assumed to be supported by all nodes.</TD></TR> </TBODY>