Alex Leong

Hi @carlislk. This means that Linkerd is unable to resolve an address. Possibly the address of the zipkin collector. How is your zipkin-http telemeter configured?

it's certainly possible, Linkerd uses the JVM dns resolver. perhaps tools like `dig` could be useful for figuring out the details of the dns setup and if the JVM is...

`(local dtab: Dtab())` simply indicates that Linkerd isn't using a routing override. You can safely ignore this. Unfortunately, I don't think the result of the DNS resolution is exposed anywhere.

Hi @mgs255! I've been trying to reproduce this but I haven't seen the behavior you described. Of course, I don't have your full cms-api environment, but I've set up some...

Hi @mgs255! Thanks so much for those logs, they were super helpful. After some investigation, I think this may be due to a race condition related to how backend services...

I typically run with a log level of `linkerd=debug,info` when I'm debugging with will cause linkerd modules to log at debug level but all other modules to log at info...

I've reviewed the outbound side of this and I think this is on the right track. I have a suggestion for how to tighten up the internal types so that...

According to the docs, this should be "first come first served": https://gateway-api.sigs.k8s.io/api-types/grpcroute/#cross-serving where the first route type should be accepted but any different route types added after should be rejected.

Hi @Sierra1011. That error log from the proxy indicated that it doesn't have any endpoints in the `Service.APP.APP:80` backend service to route to. Can you confirm that the service exists...

Hi @kastl-ars! There are certain resources which are always regenerated on install or upgrade, such as the TLS credentials for webhooks. There isn't any need for continuity of these credentials...