SonarQube - Kubernetes - LDAP - Not using sonar.properties file?

5/2/2018

This is NOT a question on how to get information to set up LDAP. This is about a specific config and issues.

Config: SonarQube: Latest running in a Tectonic Kube Cluster. Database: Postgres:latest running also in a Kube Cluster.

Issue: I put my LDAP configuration into the $SONAR_HOME/config/sonar.properties file and it's not being picked up.

Questions:

  • What I find interesting is that every line in that file is commented out, so is the server REALLY using this file or is it somewhere else?
  • If it is somewhere else, where?
  • Will changes survive a pod restart?
  • If not, how to make the changes "stick"?

Thanks all as always and let me know if I can add more information or details.

-- DC.Skells
kubernetes
ldap
sonarqube

1 Answer

5/9/2018

So, in my case, I am running SonarQube in Kubernetes. We're using TECTONIC to manage our environment.

What I ended up needing to do is make the changes to the $SONAR_HOME/config/sonar.properties file, but not directly into the server.

I ended up needing to create a new Manifest File (.yaml) to store the configuration file into a Secret Store (encrypt the properties file with base64) and the apply it as a secret.

I will have full documentation and supporting documentation on my repo soon, but I wanted to come back and close this loop.

(https://github.com/Talderon/k8s-sonarqube-golang)

-- DC.Skells
Source: StackOverflow