> For the complete documentation index, see [llms.txt](https://doc.cloudbit.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cloudbit.ch/products/kubernetes/clusters.md).

# Clusters

## Quickstart

1. Start by clicking the **Wizard** button in the [Control Panel](https://my.cloudbit.ch). Click **Create Kubernetes Cluster**.<br>
2. Choose the default configuration for your worker nodes, which determines their RAM, vCPUs, and price. If you need more than three worker nodes, click the **(+) Plus** sign on the card.<br>
3. Confirm the network topology. If you have more than one **Private Network**, you can select the one you want. By default, each cluster is assigned an [Elastic IP](#user-content-fn-1)[^1] address and is reachable via the Internet. If you wish for the cluster to be reachable only internally, uncheck the **IPv4** checkbox.<br>
4. Name your cluster and click on **Finish**. Deploying the cluster takes a few minutes.<br>
5. Download the cluster configuration file by clicking the **(**•••**) More** button and then **Download Kube-Config**.<br>
6. Once the cluster is created, use [kubectl](https://kubernetes.io/docs/tasks/tools/), the official Kubernetes command-line tool, to connect and interact with the cluster. If you prefer an intuitive graphical interface, then the free third-party tool [Lens](https://k8slens.dev/desktop.html) is right for you.

[^1]: Publicly-accessible static IP address


---

# 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://doc.cloudbit.ch/products/kubernetes/clusters.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.