# Prerequisites

Make sure these are in place before you deploy with Helm.

### Cluster and tooling

* Kubernetes `1.20+`.
* `kubectl` access to the cluster.
* Helm `v3`.

### Resources

Use the sizing guidance in [Deployment overview](/deploy-syntho/introduction.md).

If you use the bundled PostgreSQL, ensure you have a default StorageClass for PVC provisioning.

### Ingress and DNS

* An Ingress controller.
  * It must support regex in path rules (commonly NGINX).
* A DNS name that resolves to the Ingress / load balancer.
* TLS termination (Ingress + `cert-manager` or a TLS secret).

### Permissions

* Permissions to create namespaces, secrets, and deployments.
* Cluster permissions to install CRDs (Ray / KubeRay).

### Registry access

* Registry credentials for pulling Syntho images.
* Outbound network access from cluster nodes to the registry.

### Secrets and configuration

{% hint style="warning" %}
Treat deployment config as sensitive.
{% endhint %}

Common files contain secrets:

* Docker Compose: `.env`
* Kubernetes/Helm: `values.yaml`

Do not commit these files to Git.

Prefer one of these approaches:

* Inject values via your CI/CD secret store.
* Use Kubernetes Secrets (`manualSecretName`) or an external secrets operator.


---

# Agent Instructions: 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:

```
GET https://docs.syntho.ai/deploy-syntho/deploy-syntho-using-kubernetes/prerequisites.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.