DeviceTaintRule [page]deterministic

`apiVersion: resource.k8s.io/v1beta2`

`import "k8s.io/api/resource/v1beta2"`

## DeviceTaintRule {#DeviceTaintRule}

DeviceTaintRule adds one taint to all devices which match the selector. This has the same effect as if the taint was specified directly in the ResourceSlice by the DRA driver.

<hr>

<table> <thead><tr><th>Field</th><th>Description</th></tr></thead> <tbody> <tr> <td><code>apiVersion</code><br/><em>string</em></td> <td>APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources</td> </tr> <tr> <td><code>kind</code><br/><em>string</em></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/><em><a href="">ObjectMeta</a></em></td> <td>Standard object metadata</td> </tr> <tr> <td><code>spec</code>&nbsp;<strong>*</strong><br/><em><a href="">DeviceTaintRuleSpec</a></em></td> <td>Spec specifies the selector and one taint. Changing the spec automatically increments the metadata.generation number.</td> </tr> <tr> <td><code>status</code><br/><em><a href="">DeviceTaintRuleStatus</a></em></td> <td>Status provides information about what was requested in the spec.</td> </tr> </tbody> </table>

## DeviceTaintRuleSpec {#DeviceTaintRuleSpec}

DeviceTaintRuleSpec specifies the selector and one taint.

<hr>

<table> <thead><tr><th>Field</th><th>Description</th></tr></thead> <tbody> <tr> <td><code>deviceSelector</code><br/><em><a href="">DeviceTaintSelector</a></em></td> <td>DeviceSelector defines which device(s) the taint is applied to. All selector criteria must be satisfied for a device to match. The empty selector matches all devices. Without a selector, no devices are matches.</td> </tr> <tr> <td><code>taint</code>&nbsp;<strong>*</strong><br/><em><a href="">DeviceTaint</a></em></td> <td>The taint that gets applied to matching devices.</td> </tr> </tbody> </table>

## DeviceTaintRuleStatus {#DeviceTaintRuleStatus}

DeviceTaintRuleStatus provides information about an on-going pod eviction.

<hr>

<table> <thead><tr><th>Field</th><th>Description</th></tr></thead> <tbody> <tr> <td><code>conditions</code><br/><em><a href="">Condition array</a></em><br/><em>patch strategy: merge on key <code>type</code></em></td> <td>Conditions provide information about the state of the DeviceTaintRule and the cluster at some point in time, in a machine-readable and human-readable format. The following condition is currently defined as part of this API, more may get added: - Type: EvictionInProgress - Status: True if there are currently pods which need to be evicted, False otherwise (includes the effects which don't cause eviction). - Reason: not specified, may change - Message: includes information about number of pending pods and already evicted pods in a human-readable format, updated periodically, may change For `effect: None`, the condition above gets set once for each change to the spec, with the message containing information about what would happen if the effect was `NoExecute`. This feedback can be used to decide whether changing the effect to `NoExecute` will work as intended. It only gets set once to avoid having to constantly update the status. Must have 8 or fewer entries.</td> </tr> </tbody> </table>

## DeviceTaintRuleList {#DeviceTaintRuleList}

DeviceTaintRuleList is a collection of DeviceTaintRules.

<hr>

<table> <thead><tr><th>F …(trimmed)