oh gosh … so what really happened was the kubernetes upgrade from 1.17.xx to 1.18.xx. We were trailing behind with v1.18.xx
Apparently there are certain helm/sonar prereqs kube version for the sonar install which kind of screwed things up.
I didn’t dig too deep but there might be a mismatch in the versions where it did upgrade our version based on the detected version of kubernetes.
There might be a discrepancy in the allowed sonarqube version after the pod restart as it was trying to load 8.8 whereas it had us upgrade to 8.9 in the previous restart.
if that makes sense?
Solution was to push the kube version to 1.19.xx from our 1.18.xx, restart the pod, let sonar do it’s thing.
Lesson learned… keep nightly db backups anyway for peace of mind…
Thanks for the feedback, glad this community is still active.
-Harri