jaeger-operator: DNS errors in k8s

I have standard deploy in k8s, like this https://www.jaegertracing.io/docs/1.13/operator/ {"level":"info","ts":1574763937.5043714,"caller":"dns/dns_resolver.go:286","msg":"grpc: failed dns SRV record lookup due to lookup _grpclb._tcp.jaeger-collector-headless.observability.svc.cluster.local on 172.20.0.10:53: no such host.\n","system":"grpc","grpc_log":true} {"level":"info","ts":1574763937.5120873,"caller":"dns/dns_resolver.go:311","msg":"grpc: failed dns TXT record lookup due to lookup _grpc_config.jaeger-collector-headless.observability.svc.cluster.local on 172.20.0.10:53: no such host.\n","system":"grpc","grpc_log":true} {"level":"info","ts":1574763937.5121202,"caller":"grpc/resolver_conn_wrapper.go:219","msg":"ccResolverWrapper: got new service config: ","system":"grpc","grpc_log":true} {"level":"info","ts":1574763937.5121377,"caller":"grpc/resolver_conn_wrapper.go:222","msg":"ccResolverWrapper: error parsing service config: no JSON service config provided","system":"grpc","grpc_log":true} {"level":"info","ts":1574763937.5121775,"caller":"grpc/resolver_conn_wrapper.go:205","msg":"ccResolverWrapper: sending new addresses to cc: [{10.0.100.4:14250 0 <nil>}]","system":"grpc","grpc_log":true} {"level":"info","ts":1574763937.5122035,"caller":"base/balancer.go:83","msg":"base.baseBalancer: got new ClientConn state: {{[{10.0.100.4:14250 0 <nil>}] <nil>} <nil>}","system":"grpc","grpc_log":true} This ports doesn’t present in headless svc - grpclb._tcp.jaeger-collector-headless.observability.svc.cluster.local. DNS in k8s works fine. what I should do? Thx!

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 2
  • Comments: 16 (8 by maintainers)

Most upvoted comments

Yes, see #773.