> 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/platform/pricing/kubernetes.md).

# Kubernetes

### How Kubernetes pricing works

Kubernetes cluster pricing is based on the underlying required and optional Kubernetes-related resources.

{% hint style="info" %}
Starting at CHF 0.042/hr or CHF 30/mo
{% endhint %}

### Required resources

{% tabs %}
{% tab title="Worker nodes" %}
A cluster requires at least three (3) of the following worker node flavors to operate.

| Flavor²      | vCPUs |   RAM | Hourly price° | Monthly price°¹ |
| ------------ | ----: | ----: | ------------: | --------------: |
| k1.1x2       |     1 |  2 GB |    CHF 0.0090 |           CHF 7 |
| k1.2x2       |     2 |  2 GB |    CHF 0.0110 |           CHF 8 |
| k1.2x4       |     2 |  4 GB |    CHF 0.0150 |          CHF 11 |
| k1.2x8       |     2 |  8 GB |    CHF 0.0230 |          CHF 17 |
| k1.4x8       |     4 |  8 GB |    CHF 0.0270 |          CHF 20 |
| k1.4x16      |     4 | 16 GB |    CHF 0.0430 |          CHF 31 |
| k1.4x32      |     4 | 32 GB |    CHF 0.0750 |          CHF 55 |
| k1.8x32      |     8 | 32 GB |    CHF 0.0830 |          CHF 61 |
| k1.8x64      |     8 | 64 GB |    CHF 0.1470 |         CHF 107 |
| k1.8x96      |     8 | 96 GB |    CHF 0.2110 |         CHF 154 |
| k1.16x96     |    16 | 96 GB |    CHF 0.2270 |         CHF 166 |
| {% endtab %} |       |       |               |                 |

{% tab title="Control plane" %}
The following fee for the control plane (master node) per cluster applies irrespective of the cluster size.

| Flavor²       | vCPUs |  RAM | Hourly price° | Monthly price°¹ |
| ------------- | ----: | ---: | ------------: | --------------: |
| k1.2x4        |     2 | 4 GB |    CHF 0.0150 |          CHF 11 |
| {% endtab %}  |       |      |               |                 |
| {% endtabs %} |       |      |               |                 |

### Optional resources

{% content-ref url="/pages/-MZO0rzxBn-Mo-eqJkTN" %}
[Volumes & Snapshots](/platform/pricing/volumes-and-snapshots.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MZO1hTeI2VPxqA0hQnP" %}
[Load Balancers](/platform/pricing/load-balancers.md)
{% endcontent-ref %}

### Included

{% hint style="success" %}
**Elastic IP Address.** Each Kubernetes node comes with a free elastic public IPv4 address.
{% endhint %}

{% hint style="success" %}
**20 TB Outbound Traffic.** Per organization-account 20 TB of outbound traffic per month is included. Inbound and internal traffic is always free.
{% endhint %}

{% hint style="success" %}
**Basic Support** according to the best-effort principle.
{% endhint %}

° Prices are in CHF (Swiss franc) and don't include VAT. 1 CHF is usually [equal](https://www.google.com/search?q=1+CHF+in+USD\&cad=h) to 1 USD.\
¹ Monthly price estimates are based on 730 hours of usage.\
² All Kubernetes flavors are deployed with a 60 GB root volume by default.


---

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