#support

Connection Issues with k8s-infra and otel-collector Over Ingress

TLDR Saad was experiencing connectivity issues with k8s-infra and otel-collector. vishal-signoz suggested appending https in the host URL which resolved the issue.

Powered by Struct AI

1

Aug 30, 2023 (3 months ago)
Saad
Photo of md5-ecab04b75bfab44d3283f9a88ca36076
Saad
09:32 PM
Has anyone run into issues with k8s-infra trying to connect otel-collector over ingress ?

I guess this error

2023-08-30T21:30:30.674Z    warn    zapgrpc/zapgrpc.go:195    [core] [Channel #6 SubChannel #7] grpc: addrConn.createTransport failed to connect to {
  "Addr": "",
  "ServerName": "",
  "Attributes": null,
  "BalancerAttributes": null,
  "Type": 0,
  "Metadata": null
}. Err: connection error: desc = "error reading server preface: http2: frame too large"    {"grpc_log": true}
2023-08-30T21:30:37.707Z    info    exporterhelper/queued_retry.go:423    Exporting failed. Will retry the request after interval.
10:38
Saad
10:38 PM
This is my ingress spec

spec:
  ingressClassName: nginx
  rules:
  - host: 
    http:
      paths:
      - backend:
          service:
            name: rollstack-signoz-otel-collector
            port:
              number: 4317
        path: /
        pathType: ImplementationSpecific

I am using port 4317 which should be the grpc port, right?

so it’s a grpc to grpc connection but I don’t get why it’s failing

anyone knows ?
Aug 31, 2023 (3 months ago)
vishal-signoz
Photo of md5-f936d3e5743d23344d6c60813189716f
vishal-signoz
01:42 AM
> In cases of some SDKs, you would have to include https:// prefix for OTEL_EXPORTER_OTLP_ENDPOINT
01:48
vishal-signoz
01:48 AM
Saad Please try with appending https in host URL
Saad
Photo of md5-ecab04b75bfab44d3283f9a88ca36076
Saad
12:15 PM
thank you!!! it worked!!!

1