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.

Installation requirements

• Search and application nodes: The SonarQube Server Helm chart comes with default values for CPU and memory requests and limits. You may have to adjust them, depending on your system.

• Database: For information about the database requirements, see Database 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

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).

• 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.

We strongly recommend following the production use case guidelines in the Helm chart documentation.

Known limitations

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.

Problems with Azure Fileshare PVC

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.