Hello Team,
We have a requirement to set up a new version of SonarQube in a new AWS EKS cluster account and migrate the data from the sonarqube-8.9-community version. We need your help to determine the best version to upgrade to without making any breaking changes in a single attempt.
- Which version are you upgrading from? Currently, we are using SonarQube 8.9 Community version. We are considering upgrading directly to SonarQube 9.9 LTS Community version. Is it possible to upgrade directly without any issues?
- System information (Operating system, Java version, Database provider/version): We are running SonarQube Server version 8 and Scanner on version 8.
- What issue are you facing? We need guidance for a smooth upgrade and suggestions on the most feasible version to upgrade to without any breaking changes.
Here is our values.yml file for the existing SonarQube setup:
sonarqube:
initSysctl:
image: 123.dkr.ecr.ap-south-1.amazonaws/dockerhub:busybox-1.32
image:
repository: 123.dkr.ecr.ap-south-1.amazonaws/dockerhub
tag: sonarqube-8.9-community
pullPolicy: IfNotPresent
plugins:
image: 123.dkr.ecr.ap-south-1.amazonaws/dockerhub:alpine-wget-latest
install:
- "https://github.com/vaulttec/sonar-auth-oidc/releases/download/v2.0.0/sonar-auth-oidc-plugin-2.0.0.jar"
- "https://github.com/dmeiners88/sonarqube-prometheus-exporter/releases/download/v1.0.0-SNAPSHOT-2018-07-04/sonar-prometheus-exporter-1.0.0-SNAPSHOT.jar"
- "https://github.com/cnescatlab/sonar-cnes-report/releases/download/4.1.2/sonar-cnes-report-4.1.2.jar"
- "https://github.com/Inform-Software/sonar-groovy/releases/download/1.6/sonar-groovy-plugin-1.6.jar"
sonarProperties:
sonar.forceAuthentication: true
sonar.auth.oidc.enabled: true
sonar.auth.oidc.issuerUri: https://dex.internal.test.in
sonar.core.serverBaseURL: https://sonarqube.internal.test.in
sonar.auth.oidc.clientId.secured: sonarqube
sonar.auth.oidc.clientSecret.secured: 123456789
sonar.auth.oidc.loginStrategy: "Same as OpenID Connect login"
elasticsearch:
configureNode: false
bootstrapChecks: false
resources:
limits:
cpu: 6
memory: 5000Mi
requests:
cpu: 4
memory: 2500Mi
serviceAccount:
create: true
postgresql:
enabled: false
postgresqlServer: "prod-test123-south-1.rds.amazonaws"
postgresqlUsername: "sonarqube"
postgresqlPassword: "vault:secrets/data/cluster/sonarqube#postgresqlPassword"
postgresqlDatabase: "sonarqube"
serviceMonitor:
enabled: true
Thank you for your assistance in this migration process.
Best regards,
Rohan K