> For the complete documentation index, see [llms.txt](https://docs.keyless.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keyless.io/on-premise/infrastructural-requirements.md).

# Infrastructural requirements

## Kubernetes version

Currently Kubernetes version 1.34 and Openshift 4.14 on GCP are officially supported.\
Any 1.34.x version should work, but is not officially supported.\
Keyless is tested on AWS EKS and GCP GKS, respecting the Kubernetes versions mentioned.\
The nodes must be x86\_64 ones.\
Keyless Backend doesn’t support ARM architecture.

## Postgresql version

Postgresql 14+, 15+ versions are officially supported.\
A Postgres database is used used by these services to store data:

* Core Daemon Service
* Administration Dashboard Service

## S3 compatible storage

An S3-compatible backend (e.g. GCS) is needed by the following services to store data:

* Core Daemon Service

## Helm / Docker repository

The helm charts are stored in a private helm repository.\
Connection details and related authentication will be granted by Keyless upon request.

The helm charts are configured to retrieve Docker images from Keyless’ private `quay.io` repository. Access to the Docker repository must be granted by Keyless prior to installing the service.

<br>

<br>


---

# 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.keyless.io/on-premise/infrastructural-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.