-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Averaging 5000 ms Delay in Network Requests #22165
Labels
Comments
This issue is also present in Rancher 2.2.7 while using weaveworks/weave-kube:2.5.0 |
After upgrading Linux 4.15.0-1043-aws to Linux 5.2.0-050200-generic. We're seeing much faster name resolutions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Kubernetes 1.14.1
Rancher 2.2.4
Using weave CNIs:
network:
options:
flannel_backend_type: "vxlan"
plugin: "weave"
Result:
ping/curl/wget hang for othe 5ish seconds but nslookup does not.
Other details that may be helpful:
Workaround:
Add the following to dnsConfig for the pod.
This looks to be related to weaveworks/weave#3287
Environment information
rancher/rancher
/rancher/server
image tag or shown bottom left in the UI): v2.2.4The text was updated successfully, but these errors were encountered: