> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmk/how-to/how-to-rename-pmk-cluster.md).

# How To Rename PMK Cluster?

## Problem

Update or change in the cluster name.

## Environment

* Platform9 Managed Kubernetes v 5.6 and above

## Procedure

To perform cluster rename we have curl put request, which helps to rename cluster. We need "user token" and "qbert api url" to execute this request. Steps can be followed as below:

1. Get the required details as below:
   1. `Token` - Copy user token from cluster kubconfig downloaded from GUI
   2. `Request-API-URL-for-target-cluster` - On GUI - Click on Access --> API services --> qbert --> click getClusterDetails in requests method --> get copy the **Request API.**
   3. Export user token as

```javascript
# export TOKEN=<copy-it-from-cluster-kubconfig-file-for-your-user>
```

2. Execute the curl API request as below - you should see an "Ok" message at the bottom. This should start the cluster rename process. please wait for some time as the cluster will renew its certificates on all nodes. During this time cluster and nodes may not look healthy.

{% tabs %}
{% tab title="Curl put request to Update cluster" %}

```javascript
# curl --request PUT --url <Request-API-URL-for-target-cluster> --header "X-Auth-Token: $TOKEN" -H "Content-Type: application/json" --data '{ "name": "<new-cluster-name>" }'

e.g.
@ curl --request PUT --url https://gauravk.platform9.horse/qbert/v4/c98516ee2cca4744965a1e6decab3475/clusters/5bb89ce7-cf20-4c73-af26-38e58430ab0d --header "X-Auth-Token: $TOKEN" -H "Content-Type: application/json" --data '{ "name": "my-2node-cluster" }'
OK
```

{% endtab %}
{% endtabs %}

3. Verify new cluster name using curl get request

```javascript
# curl --request GET --url <Request-API-URL-for-target-cluster> --header "X-Auth-Token: $TOKEN" -H "Content-Type: application/json" | jq | grep "name"

e.g.
# curl --request GET --url https://gauravk.platform9.horse/qbert/v4/c98516ee2cca4744965a1e6decab3475/clusters/5bb89ce7-cf20-4c73-af26-38e58430ab0d --header "X-Auth-Token: $TOKEN" -H "Content-Type: application/json" | jq | grep "name"
"name": "my-2node-cluster"
```

Once cluster and every node is updated, verify the changes and check the status of cluster and nodes if all looks healthy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://platform9.com/kb/pmk/how-to/how-to-rename-pmk-cluster.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.