SONAR QUBE INSTALL
SONAR QUBE UPGRADE
SONAR QUBE SOFTWARE

Leaving persistency disabled results in a longer startup time until SonarQube is fully available, but you won't lose any data as SonarQube will persist all data in the database. You can enable persistency by adding the following to the values.yaml: persistence: By default, persistency is disabled in the Helm chart.Įnabling persistency decreases the startup time of the SonarQube Pod significantly, but you are risking corrupting your Elasticsearch index. There is an option to persist the Elasticsearch indexes in a Persistent Volume, but with regular killing operations by the Kubernetes Cluster, these indexes can be corrupted. SonarQube comes with a bundled Elasticsearch and, as Elasticsearch is stateful, so is SonarQube.

SONAR QUBE UPGRADE

Helm upgrade -install -n sonarqube sonarqube sonarqube/sonarqube

SONAR QUBE INSTALL

To install the Helm Chart from our Helm Repository, you can use the following commands: helm repo add sonarqube

Please read the following sections carefully to make the correct decisions for your environment. We try to provide a good default with the Helm chart, but there are some points to consider while working with SonarQube on Kubernetes. If you still want to use affinity and anti-affinity, see the official Kubernetes documentation. However, we generally don’t recommend using this in combination with SonarQube as it can lead to recurring rescheduling of the SonarQube pod. Node affinity and anti-affinity can be used in a way similar to node selectors but with more operators to choose from. This results in better stability and performance of SonarQube.įor more information, see the official Kubernetes documentation.

SONAR QUBE SOFTWARE

To only let SonarQube be scheduled on nodes with this specific label, add the following section to the values.yaml: nodeSelector:īy combining node selection with taints and tolerations, SonarQube can run alone on one specific node independently from the rest of your software in your Kubernetes cluster. Label the node for which you previously defined a taint with the following command: kubectl label node sonarqube=true With one node now reserved for SonarQube, you need to label this node to be selected by the Kube-scheduler in the pod assignment. Node LabelsĪs described in the Taints and Tolerations section above, for stability, we recommend binding the SonarQube deployment to one node in your cluster. To let the SonarQube deployment ignore the previously created taint, add the following section to the values.yaml: tolerations:ĭepending on your taint's name, you may need to adjust the key accordingly. This taint ensures that no additional pods are scheduled on this node. Select a node from the output of this command, and create a custom taint using the following command: kubectl taint nodes sonarqube=true:NoSchedule Use the following command to get a list of all nodes attached to your Kubernetes Cluster: kubectl get nodes In order to create a taint, you need to select a node that you want to reserve for SonarQube. The following sections detail creating a taint on a specific node and letting the SonarQube deployment ignore this taint using a flag in the values.yaml of the Helm Chart. It greatly increases the stability of the service. We recommend binding SonarQube to a specific node and reserving this node for SonarQube. MustRunAsNonRoot - There is a init container that needs to run privileged to ensure that the Elasticsearch requirements to the specific node are fulfilled.

ReadOnlyFileSystem - SonarQube is doing some filesystem operations to the container filesystem in order to deploy the correct language analyzers and community plugins.

Privileged - The SonarQube images are currently intended to start as root in order to provision the PVC and drop to lower privileges after that.

The following widely-used Pod Security Policies cannot be used in combination with SonarQube: Prerequisites SonarQube Helm Chart Kubernetes Version When you want to operate SonarQube on Kubernetes, consider the following recommendations. Your feedback is welcome at our community forum. You can find the SonarQube Helm chart on GitHub.

For information on deploying the Data Center Edition of SonarQube on Kubernetes, see this documentation. This part of the Documentation is only valid for Community, Developer, and Enterprise Editions.

Sonar qube