> For the complete documentation index, see [llms.txt](https://ai-docs.fptcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-cluster/managed-k8s-with-metal-cloud/tutorial/access-a-cluster.md).

# Access a cluster

**Step 1**: In the menu, select **Managed GPU Cluster**, and the system will display the **Managed GPU Management** page. Select the Cluster for which you want to view detailed information.

![](https://content.gitbook.com/content/2FDB5fvsiFxYI972UDTv/blobs/VhJtdKb7fJYYApRsuvFn/Unknown%20image)

**Step 2**: The **Essential Properties** tab will display the Cluster's information.

![](https://content.gitbook.com/content/2FDB5fvsiFxYI972UDTv/blobs/6ZsgS5oEF9uBXmqF8rgy/Unknown%20image)

1. **Cluster Information**: Basic information about the cluster includes:

* Cluster Name: The name assigned when the cluster was created
* Version: The version of the cluster
* Configuration: Allows you to download kube-config to communicate with the cluster
* Network: The subnet range selected when creating the cluster
* Status: The actual status of the cluster
* SSH public key: The public key information selected when creating the cluster

1. \*\*GPU Software List:\*\*Displays all GPU software installed on the cluster
2. **Load Balancer Service**: Information about the Internal LB Subnet entered
3. **API**: API URL leading to the cluster

**Step 3**: The **Node Pools** tab displays all Worker Groups belonging to the cluster and the configuration information for each Worker Group.

![](https://content.gitbook.com/content/2FDB5fvsiFxYI972UDTv/blobs/gajQQJUUD5O2YxTEwAM0/Unknown%20image)

* **Name**: Worker Group name
* **Is Based**: Display (✅) if it is a Worker base, and (✘) if it is not a Worker Base
* **Flavor Type**: Displays the selected resource flavor
* **Number of Servers**: Number of metal cloud servers for the Worker


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ai-docs.fptcloud.com/fpt-gpu-cloud/gpu-cluster/managed-k8s-with-metal-cloud/tutorial/access-a-cluster.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.