![]() The Base64 encoded certificate can be added to the secret's data: apiVersion: v1 Note that you can also use string-data here if you don't want to encode your certificate. ![]() This certificate needs to be Base64 encoded in order to be added as secret data. If you already have a running installation of your code repository platform, you can extract the certificate with the following snippet using openssl echo -n | openssl s_client -connect :443 | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > cert.pem To enable this behavior, add the following to your value.yaml file: caCerts: When you're working with your own CA or in an environment that uses self-signed certificates for your code repository platform, you can create a secret containing this certificate and add this certificate to the Java truststore inside the SonarQube deployment directly during the deployment. 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. ![]() Helm upgrade -install -n sonarqube sonarqube sonarqube/sonarqube Persistency To install the Helm Chart from our Helm Repository, you can use the following commands: helm repo add sonarqube
0 Comments
Leave a Reply. |