Context:
I am using an EKS Cluster with an AWS ALB ingress configured correctly, as I have other services running and using this same ALB without issues. However, when deploying SonarQube via Helm Chart (version 10.7.0+3598), I’m encountering a problem where the main page partially loads through the DNS, but 404 errors appear for the JS files in the browser console.
Here are the relevant settings from my values.yaml
for SonarQube:
ingress:
enabled: true
annotations:
alb.ingress.kubernetes.io/load-balancer-name: systems
alb.ingress.kubernetes.io/group.name: systems
alb.ingress.kubernetes.io/scheme: "internet-facing"
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS": 443}]'
alb.ingress.kubernetes.io/ssl-redirect: "443"
alb.ingress.kubernetes.io/backend-protocol: "HTTP"
alb.ingress.kubernetes.io/target-type: "ip"
alb.ingress.kubernetes.io/certificate-arn: arn:aws:acm:<region>:<account-id>:certificate/<arn>
external-dns.alpha.kubernetes.io/hostname: "sonarqube.dev.<mydomain>"
ingressClassName: "alb"
labels:
app: sonarqube
pathType: Prefix
hosts:
- name: "sonarqube.dev.<mydomain>"
path: "/"
serviceName: sonarqube-sonarqube
persistence:
enabled: true
storageClass: <my-storage-class>
accessMode: ReadWriteOnce
size: 5Gi
postgresql:
enabled: true
postgresqlUsername: "sonarUser"
postgresqlPassword: "sonarPass"
postgresqlDatabase: "sonarDB"
persistence:
enabled: true
size: 20Gi
account:
adminPassword: admin
currentAdminPassword: admin
adminPasswordSecretName: "sonarqube-admin-password"
Problem:
- SonarQube works correctly when I use port-forwarding in the container on port 9000.
- However, when trying to access it through the configured DNS (
sonarqube.dev.<mydomain>
), the main page loads partially, but the JS files return 404 Not Found errors.
What I have tried so far:
- I modified the
SONAR_WEB_CONTEXT
to/sonarqube
, but the 404 error for the JS files still persists.
Localhost - OK