We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
udp packet processing is done in a single go-routine (seperate go routine per k8s udp service). For scenarios like DNS, this can get slow.
(This performance issue has been fixed with the iptables proxier.)
Parallelizing the udp packet processing can be done for 1.1 (3-4 hours of work), but seems a bit risky given that we are close to 1.1 release.
This work can be done post 1.1, IF, iptables-proxier is still not the default in release 1.2
The text was updated successfully, but these errors were encountered:
#13423 (comment)
Sorry, something went wrong.
iptables-proxy is default now. closing issue.
No branches or pull requests
udp packet processing is done in a single go-routine (seperate go routine per k8s udp service).
For scenarios like DNS, this can get slow.
(This performance issue has been fixed with the iptables proxier.)
Parallelizing the udp packet processing can be done for 1.1 (3-4 hours of work), but seems a bit risky given that we are close to 1.1 release.
This work can be done post 1.1, IF, iptables-proxier is still not the default in release 1.2
The text was updated successfully, but these errors were encountered: