logo
Alauda Build of SonarQube Docs
logo
Alauda Build of SonarQube Docs
Navigation

Overview

Introduction
Features
Lifecycle Policy
Release Notes

Install

Installing Operator
Configuring PostgreSQL and Account Access Credentials
SonarQube Instance Deployment

Upgrade

Upgrading SonarQube
SonarQube Upgrade Guide from 9.9.5.1 to 2025.1.0 (Alauda Build of SonarQube Operator Version 2025.1.z)

How to

Backup and Recovery
How to Customize Deployment Templates

API Reference

Introduction

Kubernetes APIs

SonarQube
📝 Edit this page on GitHub
Previous PageFeatures
Next PageRelease Notes

#Lifecycle Policy

#TOC

#Version Lifecycle Timeline

Below is the lifecycle timeline for released versions of the Alauda Build of SonarQube operator:

VersionRelease DateEnd of Support
v2025.1.z2025-04-082026-04-08

#Release Policy

A new version of the Alauda Build of SonarQube operator is released every 1 year, updating the operator to the second-latest minor version released by SonarQube (typically using the first patch version for stability). If the SonarQube official team announces a minor version release schedule, we will also adjust our release timeline accordingly.

Differences Between Alauda and SonarQube Versions

Alauda's SonarQube operator versions are typically one minor version (4-6 months) behind the latest official SonarQube release.

#Maintenance Policy

Alauda provides 12 months of maintenance support for each released minor version of the SonarQube operator.

During the maintenance period, the following support is included:

  1. Follow up on patch versions released by SonarQube official, promptly providing patches that include bug fixes and security updates
  2. Provide security version updates that comply with Alauda's security specifications
  3. Assist customers in smoothly upgrading SonarQube operators to new versions

Additionally, Alauda will release security version updates every two months during the maintenance period to ensure the security and stability of the operators.