-
Notifications
You must be signed in to change notification settings - Fork 40.4k
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
Ipvs kube-proxy #38817
Ipvs kube-proxy #38817
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. Once you've signed, please reply here (e.g. "I signed it!") and we'll verify. Thanks.
If you have questions or suggestions related to this bot's behavior, please file an issue against the kubernetes/test-infra repository. |
@boynux @knobunc @smarterclayton @bprashanth @kubernetes/sig-network |
Is there a proposal linked to this feature? |
Jenkins Bazel Build failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins unit/integration failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins verification failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins GKE smoke e2e failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GKE smoke e2e failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins GCI GCE e2e failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE etcd3 e2e failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins GCE e2e failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Jenkins Kubemark GCE e2e failed for commit c07383f. Full PR test history. The magic incantation to run this job again is |
Ok, will write a proposal in couple of days. |
@thockin I guess we probably need different ipvs LB policies. People can enable what they want. Direct routing mode doesn't work with port mapping, definitely need other mechanisms to enable it. @mqliang Seems like current pull doesn't set LB policies. IPVS by default uses direct routing mode. Is it what you want? Considering ipvs node may be at separate nodes other than worker nodes, have you ever consider to use rest instead of direct library call. Maybe you can refer https://github.com/kobolog/gorb. NB: since there are different kube-proxy mode, shall we consider using different proxy mode for different services? for example, service A, B, C uses ha-proxy, service X, Y, Z uses ipvs, etc. |
[APPROVALNOTIFIER] Needs approval from an approver in each of these OWNERS Files: We suggest the following people: |
@mqliang PR needs rebase |
@miaoyq any plan for this PR ? we would like to explore ipvs |
I have not had time to review in depth, but I welcome people to try it and
see how it feels, what works well and what doesn't. Benchmarks might be
nice too :)
…On Tue, Feb 28, 2017 at 12:52 PM, sureshvis ***@***.***> wrote:
@miaoyq <https://github.com/miaoyq> any plan for this PR ? we would like
to explore ipvs
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38817 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFVgVB7PqT79yRoq6A5qxKx8IqM_djt0ks5rhIj7gaJpZM4LOMUc>
.
|
We have a tested implementation of IPVS kubeproxy in #44063 |
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: