Many thanks for your answer!
So it means that in the part of the helm chart that says:
I need to change this for:
I’ve already uploaded the logs in txt. Just mention here that I’ve created a MMSQL database through Azure SQL in Azure so not sure if this can be the issue here… I was reding something that creating a datatabse through Azure SQL and trying to connect the deployment to any external Azure SQL can produce some errors due to table incompatibilities.
new logs.txt (15.0 KB)
I will try to override the URL. I am not doing too much tests in Azure platform as i have very limited budget and not much experience into the platform and i don’t want to run into extra costs but definitely i will try to do that. Basically I need to set the posgres database to false and overide the url, right? something like this:
# Kubernetes secret that contains the encryption key for the sonarqube instance.
# The secret must contain the key 'sonar-secret.txt'.
# The 'sonar.secretKeyPath' property will be set automatically.
# sonarSecretKey: "settings-encryption-secret"
## JDBC Database Type; by default postgresql. To use a different Database type, adjust
## Override JDBC URL
## Configuration values for postgresql dependency
## ref: https://github.com/kubernetes/charts/blob/master/stable/postgresql/README.md
# Enable to deploy the PostgreSQL chart
# To use an external PostgreSQL instance, set enabled to false and uncomment
# the line below:
# postgresqlServer: ""
# To use an external secret for the password for an external PostgreSQL
# instance, set enabled to false and provide the name of the secret on the
# line below:
# existingSecret: ""
# existingSecretPasswordKey: "postgresql-password"
# Specify the TCP port that PostgreSQL should use
here to include the external file with the username and password i have to specify the file name in " existingSecret: " isn’t it?