Customizing the Data Center Edition (DCE) Helm chart before installation
On this page
While we only document the most pressing Helm chart customizations in this documentation, there are other possibilities for you to choose to customize the chart before installing. See the Helm chart README file and Customize the chart before installing documentation for more information on these. In particular, see the recommended production use case values.
You can customize the Helm chart:
- By editing the default values in the
values.yamlfile.
- Or directly in the Helm chart installation command line if installing from the Helm repository (see Installing the Helm chart from Helm repository).
To set up:
- Monitoring: see Setting up the monitoring of a Kubernetes deployment.
- Autoscaling: see Setting up autoscaling on Kubernetes for your Data Center Edition.
You must configure the access to your database (except if you want to use SonarQube for test purposes and want to use the embedded database H2). See Setting access to your external database in Customizing the Helm chart (Developer and Enterprise Edition).
You can:
- Enable Openshift. See Enabling Openshift in Customizing the Helm chart (Developer and Enterprise Edition).
- Ensure a restricted security level in your Openshift or Kubernetes installation, see Ensuring a restricted security level in Customizing the Helm chart (Developer and Enterprise Edition).
- Create an Ingress to make SonarQube accessible from outside. See Creating an Ingress in Customizing the Helm chart (Developer and Enterprise Edition)
- Make SonarQube Server accessible from outside. See Creating an Ingress in Customizing the Helm chart (Developer and Enterprise Edition).
If you use custom certificates for your code repository, see Using custom certificates for your code repository in Customizing the Helm chart (Developer and Enterprise Edition).
Kubernetes services automatically discover SonarQube cluster nodes, eliminating the need to specify them in a node's configuration.
Storing your JWT token
To keep user sessions alive during a restart, you need to store the JWT token you generated during pre-installation steps. To do so, store the token in the applicationNodes.jwtSecret parameter.
About persistence in Elasticsearch
SonarQube Server comes with a bundled Elasticsearch. As Elasticsearch is stateful, it makes sense to persist the Elasticsearch data for Data Center Edition (DCE) clusters because the cluster will survive the loss of any single search node without index corruption. Persistence is enabled for the DCE by default and managed with the Helm chart.
Disabling persistence would result in a longer startup time until SonarQube Server is fully available which can be a very large factor considering the downtime for the index rebuild on DCE clusters.
Related pages
Was this page helpful?
© 2008-2025 SonarSource SA. All rights reserved.
