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

Bug 1855773: Attempt to autodetect interface in nested setups #300

Merged

Commits on Jul 10, 2020

  1. Attempt to autodetect interface in nested setups

    The VLAN and macvlan nested drivers are using [binding]link_iface option
    to get the port they should bind the subport to. This isn't ideal as
    there's a single config for all kuryr-cni containers in the cluster, so
    it's impossible to provide multiple interface names when e.g. different
    VM images are used to run workers in the cluster.
    
    In order to make behavior smarter this patch makes sure that when
    aforementioned option is not set, kuryr-daemon will attempt to
    autodetect the interface it should bind the subport to by trying to find
    which iterface kubelet is bound to. This should work fine with OpenShift
    setups. If such interface is not found, kuryr-daemon will choose first
    non-loopback interface.
    
    Implements: blueprint autodetect-nested-iface
    Change-Id: I28e7d10ba4311455bc0c7fcaf28edcb30068a1e5
    dulek authored and luis5tb committed Jul 10, 2020
    Configuration menu
    Copy the full SHA
    55a9d8b View commit details
    Browse the repository at this point in the history