-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
add kube-router support #2606
Comments
Kube-router author here. If there are no objection i would like to get this option of IPVS based service proxy alternative to Kube-proxy into Kops. Like @felipejfc mentioned there are advantages using IPVS, and community gets a chance to try alernative. |
that would be very nice @murali-reddy |
Interesting. We definitely have had lots of issues (and problems debugging) with all the moving parts of K8s networking. We currently use Weave with kube-proxy. Really interested in this. |
@felipejfc @michaelajr I have intergration with Kops ready. I will raise a PR to get the changes merged in kops. Just in case you want to try patched version of kops please see the instructions https://github.com/cloudnativelabs/kube-router/blob/master/Documentation/kops.md |
fixes kubernetes#2606 Most part of the changes are similar to current supported CNI networking provider. Kube-router also support IPVS bassed service proxy which can be used as replacement for kube-proxy. So there are two changes w.r.t kubr-proxy, where when kube-router is slected for --networking flag, kube-proxy will not be launched. Current manifest for kube-router included with this patch enabled kube-router to provide pod-to-pod networking, IPVS based service proxy and ingress pod firewall.
fixes kubernetes#2606 Most part of the changes are similar to current supported CNI networking provider. Kube-router also support IPVS bassed service proxy which can be used as replacement for kube-proxy. So the manifest for kube-router included with this patch enables kube-router to provide pod-to-pod networking, IPVS based service proxy and ingress pod firewall.
fixes kubernetes#2606 Most part of the changes are similar to current supported CNI networking provider. Kube-router also support IPVS bassed service proxy which can be used as replacement for kube-proxy. So the manifest for kube-router included with this patch enables kube-router to provide pod-to-pod networking, IPVS based service proxy and ingress pod firewall.
Oh wow. We'll dig in. Thanks! |
Reading this article, kube-router seems a better choise than kube-proxy in many situations, specially if you have a kube with lots of services deployed (we have one at TFG Co)
I guess adding support for using it in Kops would be very valuable.
kube-router
The text was updated successfully, but these errors were encountered: