Best practice when deploying the helm chart of sonarqube?

Hi,

not sure if this is the right space but I am currently getting started with deploying SonarQube inside a Kubernetes Cluster with the help of the helm chart. Now the helm chart is very long (currently 720 lines) and I already read through some settings and was able to delete lines that were not necessary for me at the moment.
My question would be for the people who already deployed sonarqube: what have been your lessons while deploying it with the helm chart and what settings can you recommend on certain aspects?

I´m working with KubeOne and use ArgoCD as well so any kind of tips or recommendations that come from lots of experience would be great!

3 Likes

Hi,

I initially moved your post to the Discussions category to hopefully bring it a little more attention and get the peer responses you were asking for.

Given the underwhelming response, I’ll step in and say that we just started working on identifying the top pain points - internal and external - with the Helm chart. We hope to get the worst offenders tackled for the upcoming (Q4) LTA release.

In the spirit of that, is there anything in particular you’d like to call out for attention (other than the raw length)?

 
Ann

1 Like

Hi,
thanks!
I don´t have anything in particular to call out for attention or rather I´m not sure what would be worth mentioning. That´s why I would love to have an exchange with others to talk about it and perhaps some information might be helpful for you to note down.

Melanie

2 Likes

Hi @ganncamp We would like the ability to easily reference plugins from an internal or private repo which requires credentials to access it.
There is a long discussion about it in SUPPORT-39722 if you want to take a look there for more info and context

thanks
Tony

2 Likes