I currently have the sonarqube application deployed using helm, and I originally used the chart found at . However, this has now been deprecated and I wish to now use the helm chart at . In my old deployment of sonarqube,there was a database that had data in it. So my question is, when I deploy sonarqube again using the new helm chart, using the following commands:

helm repo add sonarqube helm repo update kubectl create namespace sonarqube helm upgrade --install -n sonarqube sonarqube sonarqube/sonarqube

will this override the data I had in my database as part of the old helm release? If so, what steps should I take to ensure the data is preserved?

1 Answer

You can pass the configuration data during helm install as given here:

I checked the sources for the sonarqube chart that you are using from here: and it had a link to the source to be here: , which has values.yaml with support for persistence. With this support you either need create your own Persistent Volume Claim and use the --set command as below:

helm upgrade --install -n sonarqube sonarqube sonarqube/sonarqube \ --set persistence.enabled=true,persistence.existingClaim=<your claim name>

Or you need to create a default Storage Class in your Kubernetes cluster and simply use command below:

helm upgrade --install -n sonarqube sonarqube sonarqube/sonarqube \ --set persistence.enabled=true

If you enable persistence then your SonarQube data will be preserved and you will be able to use when the pod or node crashes or when you are upgrading the chart to use a new SonarQube version.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.