Upon install of sonarqube via helm into a k8s cluster, the default page just sticks on ‘Loading…’
Looking at the dev console, i see that outOHS6YPPT.js and out6SLMQM3Z.css fail to load with a 404.
We are hitting the page, the tls cert shows up, the first ‘get’ request works. but nothing actually happens.
Sonarqube helm version 10.2.1 (looking to replicate a running instance and test upgrade).
kubernetes 1.24
helm upgrade --install -n testing-sq sq-test sonarqube/sonarqube -f sonar-tst-values.yaml
Blockquote
edition: “enterprise”
image:
repository: sonarqube
tag: 10.2.1-{{ .Values.edition }}
service:
type: NodePort
ingress:
annotations:
alb.ingress.kubernetes.io/certificate-arn: arn
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/subnets: subnet-A, subnet-B
alb.ingress.kubernetes.io/target-type: ip
nginx.ingress.kubernetes.io/proxy-body-size: “64m”
enabled: true
hosts:
- name: sonarqube-dev.my.domain
path: /*
initFs:
enabled: false
#image: busybox:1.32
#securityContext:
#privileged: true
#initSysctl:
#enabled: false
persistence:
enabled: true
storageClass: efs-sc
postgresql:
enabled: true
persistence:
storageClass: efs-sc-1001
postgresqlPassword: apassword
startupProbe:
initialDelaySeconds: 180
#sonarWebContext: /*