thanks for checking! After quite some posts and several trials, it’s better to quickly align on the architecture you are adopting
As far as I understood, you use the latest version of the sonarqube helm chart: 6.0.1+425. Can you confirm that?
Can you please provide us with the values.yaml and any additional (relevant) helm parameters you were using in your last test?
Which cloud provider did you use in the last test?
You mention that your pods get restarted every day. If you can disclose, what’s the reason for that?
Can you please provide the exact command you use for installing the chart against the cluster?
In addition to that, in your existing cluster, can you please check if the volume attached to SonarQube contains the plugin (that are missing) in $SONARQUBE_HOME/extensions/plugins?
Please check carefully every question, and thanks for keep testing!
We’re using Goocle Cloud as cloud provider.
The pods are restarting everyday because we’re using a certain category of pod which cost less but is restarted everyday.
We’re using helmfile to install the chart (helmfile -l name=sonarqube -i apply)
We decided to stop adding the plugins with the chart (because we’re trying since a few months and it still doesn’t works). We finally did our own sonarqube docker image with the plugins inside it and it seems to work so the problem should be solved in our side (but it still exists and i can’t more test it sorry)
We’ve recently switch to SonarQube 9.7.1-enterprise o Kubernetes, using version 5.0.6+370 of the sonarqube chart and we’ve exactly the same issue. We use one and only one plugin (OpenID Connect) and this becomes uninstalled after a few hours of runtime.
The plugin is correctly stored in the external disk (PVC):
Now, we’re just waiting to see if the problem persists.
Note that it’s likely the problem happened after the pod was relocated to another node in the cluster. In this case, using the persistence volume to fix the issue would make sense.
Hope it’ll work on your case but in ours, enabling persistance didn’t work.
the plugin was well installed but sometimes after a restart, it disappeared (and we never found why)
thanks for your contribution. May I ask if the problem happened again after ~3 weeks by now?
Indeed, from the chart point of you, we cannot really explain why a problem like this would occur when having the persistence value enabled. If plugins disappear, some (unintentional) deletion is performed on the PVC side which is not caused by our chart/application…