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
This with ip preservation normally leads to shortcircuit in kernel with src writing TLS and dst reading plain text and replying plain text but kernel doesn't know about TLS server side so protocol confusion . Maybe https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1860-kube-proxy-IP-node-binding solves the problem and sig-network slack https://kubernetes.slack.com/archives/C09QYUH5W/p1728654443481729 discuss if it is a possible fix.
The text was updated successfully, but these errors were encountered:
Another option is to implement PROXY protocol supported by NLB.
Sorry, something went wrong.
No branches or pull requests
This with ip preservation normally leads to shortcircuit in kernel with src writing TLS and dst reading plain text and replying plain text but kernel doesn't know about TLS server side so protocol confusion .
Maybe https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1860-kube-proxy-IP-node-binding solves the problem and sig-network slack https://kubernetes.slack.com/archives/C09QYUH5W/p1728654443481729 discuss if it is a possible fix.
The text was updated successfully, but these errors were encountered: