Closed mindw closed 4 months ago
Would you like to give it a try? The tricky part is that we want to disable this when Jaeger is running in Kubernetes, but we probably still want this enabled for other cases.
My personal preference would be to keep this as it is, and just suppress the message. Not sure this alone deserves a new flag...
@jpkrohling Thanks for looking at this! Alas my golang skills are non existent - but maybe common sense and some trial and error will be enough 🤔
@jpkrohling ,i want to work on this issue. could you assign me.
@jpkrohling ,i want to work on this issue. could you assign me.
Sure, I've assigned this issue to you.
If this is inactive, may I pick this up?
Go ahead I won't get it anytime soon.
nobody stepped up to fix it, and jaeger-agent is deprecated anyway, so closing
Requirement - what kind of business use case are you trying to solve?
jaeger (1.16.0) deployed in k8s 1.16 (observed at least since jaeger 1.14 and k8s 1.14).
Problem - what in Jaeger blocks you from solving the requirement?
When jaeger-agent uses its gRPC client, it issues TXT DNS queries against the in-cluster DNS pods (CoreDNS in my case), repeatedly looking up these records to find service configuration. CoreDNS does not serve these records, and the lookups prompt log messages complaining about the client's mistaken assumptions (fixed recently in coredns/coredns#2291, addressing coredns/coredns#2290).
similar issue: uswitch/kiam#204
Proposal - what do you suggest to solve the problem or improve the existing situation?
The Go gRPC client library used by kiam gained a new option in grpc/grpc-go#2010, addressing grpc/grpc-go#1998:
grpc.WithDisableServiceConfig
.potential solution: uswitch/kiam#205
Any open questions to address