> For the complete documentation index, see [llms.txt](https://documentation.planeo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.planeo.dev/getting-started/clusters.md).

# Clusters

Before Planeo can deploy applications it needs to know where to deploy them to. Rather than having Planeo pick a context, we prefer an opt-in approach where users specifically map Planeo Clusters to specific Kubernetes contexts they want to use. This helps contextualize different access paths to different K8s endpoints, around different purposes.

Planeo will load discoverable clusters from your standard configuration files, and present them as options. Non standard locations are not currently supported. Pick a name for a context, and select a kubeconfig file from the dropdown, and then select a path.

<figure><img src="/files/1KYC9vw3u3DE7gpn4SKD" alt=""><figcaption></figcaption></figure>

After clicking **Add** your cluster should get verified and added. Unless there are issues, it should enter a green "ready" status, and be available for use.

<figure><img src="/files/rI14rSOfWtKBgQkWQRLS" alt=""><figcaption></figcaption></figure>

If your cluster becomes unreachable, either because a local test cluster has stopped or perhaps auth has expired, the status will become errored in Planeo. A cluster being in a non-ready state prevents updates to dependent environments and stacks from taking place until the cluster is reachable again. This is often reflected as stacks going into a pre-ready state or an error state.&#x20;

<figure><img src="/files/lCo6ZsHrg8vxW81mSS2X" alt=""><figcaption></figcaption></figure>

As soon as the cluster becomes available again you can refresh the cluster via the UI, and it should cascade to all associated environments and stacks, so if you fix the issue, ensuring kubectl works with the referenced context, just click on the refresh icon in the actions column.


---

# 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://documentation.planeo.dev/getting-started/clusters.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.