> 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.0.0/guides/deployment-guide/deployment-on-kubernetes/k8s-cluster-requirements.md).
# K8s Cluster Requirements
Work in progress
## Hardware requirements
### For sandbox setups
| Purpose | vCPUs | RAM | Storage (SSD) | Number of Virtual Machines* | Preferred Operating System |
|---|
| Cluster nodes | 8 | 32 GB | 128 GB | 3 | Ubuntu Server 20.04 |
| Wireguard | 4 | 16 GB | 64 GB | 1 | Ubuntu Server 20.04 |
### For staging setups
| Purpose | vCPUs | RAM | Storage (SSD) | Number of Virtual Machines* | Preferred Operating System |
|---|
| Cluster nodes | 8 | 32 GB | 128 GB | 3 | Ubuntu Server 20.04 |
| Wireguard | 4 | 16 GB | 64 GB | 1 | Ubuntu Server 20.04 |
| Backup | 4 | 16 GB | 512 GB | 1 | Ubuntu Server 20.04 |
### 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 |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| - openg2p.\
- uat.\
- pilot.openg2p.\
| "A" Record mapped to Load Balancer IP **or** at least 3 nodes of the K8s Cluster |
| - *. openg2p.\
- *.uat.\
- \*.pilot.openg2p.\
| "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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openg2p.org/1.0.0/guides/deployment-guide/deployment-on-kubernetes/k8s-cluster-requirements.md?ask=&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.