Skip to content
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

Guidelines to apply this to existing openshift cluster #1

Open
Lagari-1 opened this issue Nov 9, 2024 · 1 comment
Open

Guidelines to apply this to existing openshift cluster #1

Lagari-1 opened this issue Nov 9, 2024 · 1 comment

Comments

@Lagari-1
Copy link

Lagari-1 commented Nov 9, 2024

Hi,

I was looking for a way to use services over additional networks and found this repo.

I was wondering if I can use this on a openshift cluster as it is. If so, do you have guides other than PoCs?

"Controllers must be re-written to be fully functional. They are currently written only to make the demos to work."

About above comment, What are the limitations with current controllers and is there any plan to implement it fully?

My use case is that, i have to use different networks for network separation. Since services are designed to use default network, i am not able to use service and have to go with pod-to-pod (over secondary network) communication. And this limits scalability and some other benefits of services. As I understand, this repo promise what i am looking for!

Thanks in advance. Great work!
@LionelJouin
Copy link
Owner

Hi,

Thank you for your interest in this area.

Yes, you could use Openshift if your cluster fulfills the requirements of this PoC. A thesis student tried a previous version of this PoC on Openshift, here is his thesis: https://mdh.diva-portal.org/smash/get/diva2:1871248/FULLTEXT01.pdf

The limitation of these controllers is that they are not fully and properly tested, they are mainly developed for this PoC. I tried to push some of the limitation and controller to Kubernetes directly: kubernetes/enhancements#4771

Yes, I have plans to implement it, but I am first looking for collaboration with some other people so we could create a community around it.
My plan would be to divide the project into 2 parts:

  • MetalLB-like working on secondary interfaces with a BGP speaker in the pod (instead of the node).
  • L3/4 Router / Load-Balancer. This might need some improvement of Gateway API.

Just so you know, this PoC is mainly for traffic originating from outside of the cluster. I haven't investigated the ClusterIP type of services.

You might also be interested into Calico-VPP that has an implementation of Multi-Network Services (https://github.com/projectcalico/vpp-dataplane/blob/master/docs/multinet.md), and LoxiLB that supports Multus (from what I understood) (https://www.loxilb.io/).

You can reach me directly on Slack if you want to discuss more about it: https://kubernetes.slack.com/team/UKTTRNJ84

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LionelJouin @Lagari-1