> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/1.1/guides/deployment-guide/deployment-on-kubernetes/k8s-cluster-requirements.md).

# K8s Cluster Requirements

## Hardware requirements

### For sandbox setups

<table><thead><tr><th width="136">Purpose</th><th align="center">vCPUs</th><th align="center">RAM</th><th align="center">Storage (SSD)</th><th align="right">Number of Virtual Machines*</th><th>Preferred Operating System</th></tr></thead><tbody><tr><td>Cluster nodes</td><td align="center">8</td><td align="center">32 GB</td><td align="center">128 GB</td><td align="right">3</td><td>Ubuntu Server 20.04</td></tr><tr><td>Wireguard</td><td align="center">4</td><td align="center">16 GB</td><td align="center">64 GB</td><td align="right">1</td><td>Ubuntu Server 20.04</td></tr></tbody></table>

### For staging setups

<table><thead><tr><th width="136">Purpose</th><th align="center">vCPUs</th><th align="center">RAM</th><th align="center">Storage (SSD)</th><th align="right">Number of Virtual Machines*</th><th>Preferred Operating System</th></tr></thead><tbody><tr><td>Cluster nodes</td><td align="center">8</td><td align="center">32 GB</td><td align="center">128 GB</td><td align="right">3</td><td>Ubuntu Server 20.04</td></tr><tr><td>Wireguard</td><td align="center">4</td><td align="center">16 GB</td><td align="center">64 GB</td><td align="right">1</td><td>Ubuntu Server 20.04</td></tr><tr><td>Backup</td><td align="center">4</td><td align="center">16 GB</td><td align="center">512 GB</td><td align="right">1</td><td>Ubuntu Server 20.04</td></tr></tbody></table>

### For production setups

TBD

## Networking requirements

* All the machines in the same network.
* Public IP assigned to the Wireguard machine.

## DNS requirements

The following domain names and mappings will be required. Examples:

| Domain Name (examples)                                                                                                                    | Mapped to                                                                        |
| ----------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| <ul><li>openg2p.<em>\<your domain></em></li><li>uat.<em>\<your domain></em></li><li>pilot.openg2p.<em>\<your domain></em></li></ul>       | "A" Record mapped to Load Balancer IP **or** at least 3 nodes of the K8s Cluster |
| <ul><li><em>. openg2p.\<your domain></em></li><li>.uat.<em>\<your domain></em></li><li>\*.pilot.openg2p.<em>\<your domain></em></li></ul> | "CNAME" Record mapped to the above domain. (This is a wildcard DNS mapping)      |

## Certificate requirements

One wildcard certificate is required at least, depending on the above domain names used. This can also be generated using letsencrypt.


---

# 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://docs.openg2p.org/1.1/guides/deployment-guide/deployment-on-kubernetes/k8s-cluster-requirements.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.
