# Deauthorize-node Command

The `pf9ctl deauthorize node` will deauthorize the node on which the command is run, marking it as unusable until the user re-authorizes it. If the node is a part of a single node cluster, or if it is the master node, the user is notified that the cluster is now disconnected. The deauthorization process typically takes under a minute to show up in the UI.

## Syntax Example

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

```bash
pf9ctl deauthorize-node
```

{% endtab %}
{% endtabs %}

## All Available Commands and Flags

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

```bash
# pf9ctl deauthorize-node --help
Deauthorizes this node. It will warn the user if the node was a master node or a part of a single node cluster.

Usage:
  pf9ctl deauthorize-node [flags]

Flags:
  -h, --help         help for deauthorize-node
      --mfa string   MFA token

Global Flags:
      --no-prompt   disable all user prompts
      --verbose     print verbose logs
```

{% endtab %}
{% endtabs %}

## Command Example

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

```bash
# pf9ctl deauthorize-node
✓ Loaded Config Successfully
Node deauthorization started....This may take a few minutes....Check the latest status in UI
```

{% 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://docs.platform9.com/managed-kubernetes/pmk-cli/commands/cli-deauthorize-node.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.
