Community Build on k8s (kubernetes) limitations

SonarQube Server / Community Build
, ,
1

Hi,
So far we’re using Sonarqube community build (9.9.3) that runs in a docker container on EC2 host, using RDS (postgres database). This is a single instance of Sonarqub and as a prod environment, we’d like to enhance it with some HA. The optimal solution would be EKS cluster but it was found in the documentation that:

As SonarQube Community Build is intended to be run anywhere, there are some drawbacks that are currently known when operating in Kubernetes. This list is not comprehensive, but something to keep in mind and points for us to improve on.

Do you have those drawbacks listed, known? Any feedback from others about running community build on k8s?
Alternatively - maybe another approach to HA installation?

Thanks

2

Hey there.

They’re listed below that section in the docs. Readiness and startup delays and Problems with Azure Fileshare PVC.

In fact, the limitation you’ll find for running SonarQube Community Edition/Build as a cluster is not in the Kubernetes implementation, but that deploying SonarQube with multiple nodes / in a cluster config is only available in SonarQube Server’s Data Center Edition.

3

Thanks for your reply