Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

How to implement Virtual Service IP in weave? #3941

Open
KendrickChou opened this issue May 13, 2022 · 1 comment
Open

How to implement Virtual Service IP in weave? #3941

KendrickChou opened this issue May 13, 2022 · 1 comment

Comments

@KendrickChou
Copy link

Hi! I'm using weave as the cni plugin to create a self-made mini k8s cluster. To support services, I need to map a virtual service ip(e.g. 10.6.6.6) to several container ip(e.g. 10.30.0.1, 10.30.0.2) which are allocated by weave. The problem is:
How can I convert the virtual service ip to a container ip before the packet was send to Weave Router to be encapsulated in a tunnel protocol header?
I've tried using DNAT in iptables, but it doesn't work. I think the problem is although I change the packet destination (e.g. 10.6.6.6 -> 10.30.0.1), the packet will not be sent to Weave Router to add a tunnel protocol header.
Much appreciation for your help :)

@KendrickChou
Copy link
Author

KendrickChou commented May 13, 2022

I notice that someone commited a similar issue in 2015: IP load balancing and it was added to milestones, but it doesn't seem to have been solved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant