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.

Sign up for GitHub

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

Jump to bottom

make kube-router service VIP advertisement functionality independently usable. #392

Closed

murali-reddy opened this issue Apr 13, 2018 · 1 comment

Labels

Member

murali-reddy commented Apr 13, 2018

Network routes controller in kube-router does two crticial jobs now.

advertise pod CIDR's allocated to the nodes to the peer nodes, extenal peers etc
Advertise the service VIP's to the external peers.

I think its useful to have the functionality of #2, independent of #1.

Which mean, i should be use Flannel/Weave as CNI, yet deploy kube-router's and can use its service proxy and VIP advertisement capability.

Its not a big change at all, but need clear documetnation on presecribing what flags to use when.

murali-reddy added the enhancement label

Collaborator

aauren commented Apr 24, 2020

While documentation is always nice, I think there is a good amount in other projects on how to integrate with kube-router's BGP functionality such as: https://docs.cilium.io/en/v1.2/kubernetes/install/kube-router/

aauren closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment