# Before you start

## Installation requirements <a href="#installation-requirements" id="installation-requirements"></a>

* Search and application nodes: The SonarQube Server Helm chart comes with default values for [CPU and memory requests and limits](https://artifacthub.io/packages/helm/sonarqube/sonarqube-dce#cpu-and-memory-settings). You may have to adjust them, depending on your system.
* [database-requirements](https://docs.sonarsource.com/sonarqube-server/2025.2/setup-and-update/installation-requirements/database-requirements "mention") requirements.
* Kubernetes, OpenShift, and Helm versions: The Helm chart documentation provides information about the supported Kubernetes and OpenShift versions.
* Helm: Version 3 must be used.

## Production use case <a href="#production-use-case" id="production-use-case"></a>

In a production use case:

* Ensure that the SonarQube Server Helm chart runs in a full restricted namespace (see **Ensuring a restricted security level** in [Customizing the Helm chart](https://docs.google.com/document/d/1pY7uTzdTvQQ2GLccjilm1xLSBVFoXSecvLl54ETm-2M/edit#heading=h.fu9rwwn08f6q)).
* Use your own Ingress controllers.\
  Ingress controllers are critical Kubernetes components, we advise users to install their own.
* Use your own database.

The DCE Helm chart can deploy a PostgreSQL database. This database should be used for test purposes only.

{% hint style="info" %}
We strongly recommend following the [production use case guidelines](https://artifacthub.io/packages/helm/sonarqube/sonarqube-dce#production-use-case) in the Helm chart documentation.
{% endhint %}

## Known limitations <a href="#known-limiations" id="known-limiations"></a>

As SonarQube Server is intended to be run anywhere, there are some drawbacks that are currently known when operating in Kubernetes. This list is not comprehensive, but something to keep in mind and points for us to improve on.

### Limitation with Azure Fileshare PVC <a href="#limitation-with-azure-fileshare-pvc" id="limitation-with-azure-fileshare-pvc"></a>

Currently, there is a known limitation when working with AKS due to the way Azure Fileshare uses NTFS, which cannot handle the file system permissions and properties that SonarQube Server relies on. We recommend using another storage class for persistence on AKS.