Update Helm release sonarqube to v2025.3.1
This MR contains the following updates:
Package | Update | Change |
---|---|---|
sonarqube (source) | minor |
2025.1.0 -> 2025.3.1
|
Complete MR checklist
Umbrella Branch
sonarqube-test-values
Assignee
-
Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md -
Update Docs with new/updated steps as needed -
Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines
Add supporting info below
Screen cap of the cypress tests running on an upgraded sonarqube instance on k3d just to confirm not setting an admin password via helm still works as expected in our testing. Screen_Recording_2025-09-16_at_2.41.09_PM
Reviewer only
-
Tested and Validated changes
❗ ImportantRelease Notes retrieval for this MR were skipped because no github.com credentials were available. If you are self-hosted, please see this instruction.
Configuration
-
If you want to rebase/retry this MR, check this box
This MR was automatically generated by Renovate Bot.
Upgrade Notices
If you use the helm values account.adminPassword
or setAdminPassword.newPassword
to set the default admin password for this chart, you may run into a problem where upon upgrading, the helm release will try and keep running the update script from the upstream template change-admin-password-hook.yaml
. This will eventually fail causing the helm release to try installing again. If you have set the values you can either remove them from your values file before upgrading or you can change the secret (I.E. sonarqube-sonarqube-admin-password
) that gets created and set the currentPassword
to value of the current admin password.