Encountering an error (default-backend:80 not found) during Grafana installation with Helm using an external DNS and ALB ingress setup. Consider the following alternative configuration:
routing:
enabled: true
ingressClass: alb
options:
host: dashboard.example.com
scheme: public
tlsArn: arn:aws:acm:region:account:certificate/new-cert
ports: '[{"port": 8080}, {"port": 8443}]'
backend:
serviceName: grafana-service
servicePort: http
path: /dash/
hey, i’m wondering if its a naming mismatch? i had a similar issue and realized my service name was slightly off. maybe double-checking your ingress and service configurations could help. anyone else run into this? what tweaks did u make?
hey, i had a simmilar prob once. end up correcting my service name in the backend config. helm sometimes uses defult values if not precise. maybe double-check your service mappings and names for consistency. hope it helps!
The error seems to be related to an unintentional reliance on default configurations not suited for the specific ingress controller setup in your deployment. In my recent experience, I found that explicitly setting values for the default backend in the Helm chart configuration prevented the system from trying to locate a nonexisting service. It is important to double-check that your ingress annotations and device-specific settings are aligned with your infrastructure, particularly when combining external DNS with an ALB ingress. This approach helped me bypass similar issues and achieve a smoother deployment.