-
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
Accessing NodePort on K8S host has latency when reaching Pods across different hosts #1859
Comments
The issue manifests as follows: When curling the cluster IP, if the request is directed to a pod across different hosts, it takes 1 second to receive a response. However, if the request is directed to a pod on the same host, the response speed is normal. Upon packet analysis, it is observed that the initial connection to flannel.1 is reset, causing a 1-second delay. flannel:v0.20.1 |
There are known issues with hardware offload on some platforms as explained in the issue you linked above. This isn't an issue that we can solve from flannel as it is more likely tied to the specific kernel/harware combination that is used. |
@thomasferrandiz What are some graceful ways to solve/avoid this issue? |
See:kubernetes/kubernetes#122835
I don't quite understand the reason for the issue. Is it a bug in the operating system kernel or in Flannel? How can it be fixed?
The text was updated successfully, but these errors were encountered: