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.

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

Support multiple pod networks #104

Open
Cerebus opened this issue Aug 26, 2021 · 3 comments
Open

Support multiple pod networks #104

Cerebus opened this issue Aug 26, 2021 · 3 comments

Comments

@Cerebus
Copy link

Cerebus commented Aug 26, 2021

Multiple CNIs can run in parallel, creating multiple data planes in a Kubernetes cluster. Goldfinger should allow me to ping over an arbitrary data plane.

It would seem that POD_IP is the place to set this, but when I set POD_IP for each goldpinger pod to an IP on an alternative dataplane, this setting is lost after discovery; goldpinger finds the peer pods but uses the primary data plane IP addresses.

Not all data planes are discoverable from the Pod API. E.g., Multus data plane specs are in Pod annotations. Meshnet-CNI specs data planes in a CRD that refers to a Pod resource by name.

@seeker89
Copy link
Contributor

While a little niche, I think that's a good idea. I wonder how we'd discover the alternative IPs, if they can't be provided by the Pod API (getting them from annotations would be straightforward).

I'd be happy to review a PR, let's just make sure we still default to the current behaviour.

@Cerebus
Copy link
Author

Cerebus commented Aug 27, 2021

Can someone better explain what POD_IP is supposed to do? That would be the place I'd start.

@seeker89
Copy link
Contributor

POD_IP is just a way for letting Goldpinger know its IP, to print better graphs.

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

No branches or pull requests

2 participants