> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2025.1/setup-and-upgrade/deploy-on-kubernetes/dce/before-you-start.md).

# Before you start

This page describes the requirements and known limitations of a SonarQube Server’s Data Center Edition (DCE) deployment on Kubernetes or Openshift. This page is for SonarQube Server 2025.1.

## 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: For information about the database requirements, see [Database](/sonarqube-server/2025.1/setup-and-upgrade/installation-requirements/database-requirements.md).
* Kubernetes, OpenShift, and Helm versions: The Helm chart documentation provides information about the supported Kubernetes and OpenShift versions.
* Helm: Version 3 must be used.

{% hint style="warning" %}
ArgoCD-based deployments of the SonarQube Helm chart are not currently fully supported or validated.
{% endhint %}

## 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 [Customizing Helm chart](/sonarqube-server/2025.1/setup-and-upgrade/deploy-on-kubernetes/dce/customizing-helm-chart.md#ensuring-restricted-level)).
* 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.


---

# 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.sonarsource.com/sonarqube-server/2025.1/setup-and-upgrade/deploy-on-kubernetes/dce/before-you-start.md?ask=<question>&goal=<user_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.