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

How to create additional interfaces on compute nodes #644

Open
njayakrishna opened this issue Apr 8, 2022 · 2 comments
Open

How to create additional interfaces on compute nodes #644

njayakrishna opened this issue Apr 8, 2022 · 2 comments
Labels

Comments

@njayakrishna
Copy link

Hi,
I wanted to know how do we modify the inventory file to created multiple interfaces on the compute nodes.
Currently when I am running the script, all the compute/worker node VMs get one interface installed, e.g.: enp1s0/10.0.0.2 with the gateway assigned to tun0 (10.0.0.254 address on LR0) and the OVN components programmed accordingly.
My requirement is to configure an additional interface (e.g. enp7s0/11.0.0.2 with gateway 11.0.0.254) on the compute nodes and the gateway getting configured on the same lines as the first interface/network.
Is there a way that the current implementation of KubeInit can do this?
Thanks in advance for your help.

@ccamacho
Copy link
Collaborator

Hi,

So far adding additional interfaces to the compute nodes is not supported, maybe if you could share your use case we could add it in the future.

@njayakrishna
Copy link
Author

Hi Camacho,
The use case is for multiple interfaces for pods running on the worker nodes. As you are aware this is typically achieved using secondary CNIs using multus CNI. When we have these extra or secondary interfaces in the pods, we want to be able to specify a separate interface on the worker node VMs as the 'master' field in the CNIs, so that the pod's secondary interface traffic land in these newly created interfaces on the worker node VMs.
From my understanding of the Kubeinit networking model, my request is to have a second bridge installed. Please correct me if I am wrong:

  1. Similar to the bridge kimgtnet0 catering to 10.0.0.x network, we would require another bridge say kimgtnet1 catering to the new subnet 20.0.0.x.
  2. We would then need to create a new gateway say 20.0.0.254 on the LR0 router similar to the gateway for 10.0.0.0 subnet.

Would be it possible to incorporate this via the ansible script with the option in the inventory file?
Thanks for your time.

-Jayakrishna

@ccamacho ccamacho added the keep label May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants