# Uncordon Node After Maintenance to Make it Schedulable Again

## Problem

The Drain node operation being performed on nodes prior to the maintenance of hypervisors results in nodes to be in a **Ready, SchedulingDisabled** state once the maintenance is completed.

{% tabs %}
{% tab title="None" %}

```none
NAME            STATUS                ROLES    AGE  VERSION
NodeName   Ready,SchedulingDisabled   worker   34d  v1.12.9
```

{% endtab %}
{% endtabs %}

The nodes will have **NoSchedule** taints on them.

{% tabs %}
{% tab title="None" %}

```none
Taints:            node.kubernetes.io/unreachable:NoSchedule                   node.kubernetes.io/unschedulable:NoSchedule
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed Kubernetes - All Versions

## Resolution

* Uncordon the nodes to make them schedulable again, thus resuming the procedure of scheduling pods onto it.

{% tabs %}
{% tab title="None" %}

```none
# kubectl uncordon [node name]
```

{% endtab %}
{% endtabs %}

## Additional Information

[Safely Drain Node](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://platform9.com/kb/pmk/solutions/uncordon-node-after-maintenance-to-make-it-schedulable-again.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.