I am working on deploying Sonarqube 8.9 LTS on Kubernetes using the associated Helm chart.
I’m having trouble understanding how to pull additional sonar properties from a secret. In my case, I have a custom sonar.properties file, and I would like to provide a value for my property
ldap.bindPassword from an external secret. Can someone explain how this can be achieved?
sonarProperties: ldap.url : some.url.com ldap.bindPassword: <my value from an external secret>
values.yaml file reads the following:
# Additional sonar properties to load from a secret with a key "secret.properties" (must be a string) # sonarSecretProperties:
I’m unclear with what that means or how to use it. In contast, providing a password for the postgres database seems a bit more intuitive --I describe it below to contrast.
This is easy enough for setting up credentials of the postgres password (a seperate task that I understand and have been able to use). You simply provide the
existingSecret, which is the name of the secret, and the
existingSecretPasswordKey, which is the key associated with the postgres password.