Hello Team,
Could you please assist me with an issue I'm facing? I have installed and configured SigNoz on an AWS EKS cluster. It is working as expected with the OTEL collector endpoint pointing to the default service/pod endpoint like this:
otlp:
endpoint: <http://signoz-otel-collector.platform.svc.cluster.local:4317>
Our team has requested to externalize this endpoint using Ingress, so we can use the same endpoint across different clusters instead of configuring OTEL in each cluster. We have installed the AWS Load Balancer Controller to use as the ingress controller. I created an Ingress resource using the following specification referenced in the Helm values file:
otelCollector:
ingress:
# -- Enable ingress for otelCollector
enabled: true
# -- Annotations to otelCollector Ingress
annotations:
alb.ingress.kubernetes.io/load-balancer-name: signoz-collector-lb
kubernetes.io/ingress.class: alb
alb.ingress.kubernetes.io/scheme: internet-facing
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80}, {"HTTPS":443}]'
alb.ingress.kubernetes.io/certificate-arn: arn:aws:acm:us-east-2:XXXXXXXXX:certificate/XXXXXXXXXXX
alb.ingress.kubernetes.io/ip-address-type: ipv4
alb.ingress.kubernetes.io/target-type: ip
# -- Frontend Ingress Host names with their path details
hosts:
- host: <HOST_URL>
paths:
- path: /
pathType: ImplementationSpecific
port: 4318
I was able to create the Load Balancer, but it is failing the health check, which prevents access to the endpoint from outside. Can someone please check and help me resolve this issue?
I am using EKS version 1.27 and the Helm chart version is "signoz-0.44.0".
