DNS canonicalize failed to refine #2069
Description
Bug Report
What is the issue?
Services with Linkerd sidecar are working fine. But the Linkerd sidecar logs show constant DNS errors.
How can it be reproduced?
N/A
Logs, error output, etc
ERR! linkerd2_proxy::proxy::canonicalize failed to refine catalyst.elasticsearch.service.azure-west-us.consul: deadline has elapsed
ERR! linkerd2_proxy::proxy::canonicalize failed to refine catalyst.elasticsearch.service.azure-west-us.consul: deadline has elapsed
ERR! linkerd2_proxy::proxy::canonicalize failed to refine catalyst.elasticsearch.service.azure-west-us.consul: deadline has elapsed
ERR! linkerd2_proxy::proxy::canonicalize failed to refine catalyst.elasticsearch.service.azure-west-us.consul: deadline has elapsed
ERR! linkerd2_proxy::proxy::canonicalize failed to refine catalyst.elasticsearch.service.azure-west-us.consul: deadline has elapsed
ERR! linkerd2_proxy::proxy::canonicalize failed to refine portfolio.kyro.svc.cluster.local: deadline has elapsed
linkerd check output
$ linkerd check
kubernetes-api: can initialize the client..................................[ok]
kubernetes-api: can query the Kubernetes API...............................[ok]
kubernetes-api: is running the minimum Kubernetes API version..............[ok]
linkerd-existence: control plane namespace exists..........................[ok]
linkerd-existence: controller pod is running...............................[ok]
linkerd-existence: can initialize the client...............................[ok]
linkerd-existence: can query the control plane API.........................[ok]
linkerd-api: control plane pods are ready..................................[ok]
linkerd-api: can query the control plane API...............................[ok]
linkerd-api[kubernetes]: control plane can talk to Kubernetes..............[ok]
linkerd-api[prometheus]: control plane can talk to Prometheus..............[ok]
linkerd-api: no invalid service profiles...................................[ok]
linkerd-version: can determine the latest version..........................[ok]
linkerd-version: cli is up-to-date.........................................[ok]
linkerd-version: control plane is up-to-date...............................[ok]
Status check results are [ok]
Environment
- Kubernetes Version: v1.11.5
- Cluster Environment: AKS
- Host OS: Amazon Linux
- Linkerd version:
Client version: edge-19.1.1
Server version: edge-19.1.1
Possible solution
N/A
Additional context
I switched over to Edge due to issue #2012. My cluster is configured to use CoreDNS, proxying requests for .consul domain to the local consul DNS service. I'm not sure if this has anything to do with the logged errors.