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

One-to-one mapping fallback between "via" interface and "base" interface. #276

Open
tedlean opened this issue Feb 1, 2023 · 0 comments
Open

Comments

@tedlean
Copy link

tedlean commented Feb 1, 2023

When establishing an interface, the forwarder makes a lookup in a configMap to find the mapping between the name of the interface to create and the name of the host interface to use. This way the host interface can be reached "via" one or more interface name aliases. If the name of the interface to create cannot be found in the list of "via" aliases the interface will not be create.

This means that ConfigMap very often have to be adapted to the actual cluster environment, also in the most normal case where the mapping simply is one-to-one, like eth5 via eth5.

The proposal is to extend the current functionality to first look in the configMap as of today, but if not found here, simply try to use a one-to-one mapping as a fall-back.

@LionelJouin LionelJouin moved this to 📋 To Do in Meridio Feb 1, 2023
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

1 participant