# Nodelet Does Not Remove The Node From Kubernetes Cluster When Node Is Removed From Qbert Cluster

## Problem

* The kubectl command is still listing the master node that has been scaled down from UI.

## Environment

* Platform9 Managed Kubernetes - v5.4 and above

## Cause

* The task of removing the scaled down node from the kubernetes cluster is handled by the `all-none-scripts.sh` phase script which runs when `ROLE=”none”` and `KUBE_SERVICE_STATE=false` is set in the config.
* However there is a possibility that the certs are removed prior to this which causes node removal to be skipped because the node cannot reach the other master nodes or master VIP.

## Resolution

* A internal JIRA ticket [PMK-5585](https://platform9.atlassian.net/browse/PMK-5585) has been raised to fix this issue.
* The workaround for this issue is, post node scale down wait for the node and cluster to get converged in the Platform9 UI, and then delete the node from the cluster using below mentioned command.

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

```javascript
# kubectl delete node <scaled_down_node>
```

{% endtab %}
{% endtabs %}


---

# 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/nodelet-does-not-remove-the-node-from-kubernetes-cluster-when-no.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.