> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nodewright/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nodewright/_mcp/server.

Just like any other scheduler NodeWright will not schedule packages on selected nodes when there are taints that the package does not explicitly tolerate. These nodes however are not just ignored as it is assumed that the user wanted their packages on these nodes due to their selection of nodeSelectors. In this case the following will happen:

On the NodeWright Custom Resource containing the package(s) targeting the affected nodes:

```yaml
status:
    status: blocked
    nodeStatus:
        [node name]: blocked
    conditions:
      - reason: TaintNotTolerable
        status: "True"
        type: TaintNotTolerable
        message: Node [X, Y, Z, ...] has taints that are not tolerable. Skipping.
```

The legacy prefixed `nodewright.nvidia.com/TaintNotTolerable` condition type is retained for one release to allow existing consumers time to migrate.

Metrics:

 * nodewright_node_status_count status=blocked

# Default tolerations

The following taints are always tolerated by NodeWright

 * Runtime Required (`controllerManager.manager.env.runtimeRequiredTaint`, default `nodewright.nvidia.com=runtime-required:NoSchedule`)
 * Runtime Required, legacy key: `skyhook.nvidia.com=runtime-required:NoSchedule`. Tolerated and removed for the rename deprecation window, never applied. See [runtime_required.md](/nodewright/user-guide/runtime-required#taint-key-rename-skyhooknvidiacom---nodewrightnvidiacom).
 * Cordon taint: `node.kubernetes.io/unschedulable`

# Common Symptoms

The following are common ways a user might know they have taint problem:

1. A NodeWright Custom Resource has status as `unknown` (Operator < v0.9) or `blocked` (Operator >= v0.9)
2. A NodeWright Custom Resource is sitting with incomplete nodes.

# Solutions

This can be solved in a few different ways:

 1. Remove the problem taint(s) from the node(s)
 2. Change the `nodeSelectors` for the NodeWright Custom Resources to avoid the nodes
 3. Set the `additionalTolerations` on the NodeWright Custom Resources to enable toleration of the taints. An example doing this is included below.

 ```yaml
 apiVersion: nodewright.nvidia.com/v1alpha1
kind: NodeWright
metadata:
  labels:
    app.kubernetes.io/part-of: skyhook-operator
    app.kubernetes.io/created-by: skyhook-operator
  name: taint-scheduling
spec:
  nodeSelectors:
    matchLabels:
      nodewright.nvidia.com/test-node: skyhooke2e
  additionalTolerations:
    - key: nvidia.com/gpu
      effect: NoSchedule
  packages: ...
```