newbie question about multus-cni

[dougbtv]

If you're going to use Multus, and one of the network attachments you'd like to create is for Flannel -- then that example will probably work. There's also an updated example in this jinja2 templates (if you're not templating it, change out items in {{ double curly braces }} with something static), in that particular example -- it's Multus with two interfaces -- one for flannel, and one for macvlan.

So, the end goal of that example in #3 and the example I posted here is that it does two things -- one, it instantiates Flannel pods, AND most importantly (in terms of Multus) -- it drops a .conf file for CNI on each host, as it's starting a daemonset which then has a container which mounts a host directory and then writes a configuration file to it.

[verizonold]

@dougbtv I ran into a issue with adding a node after the cluster was created successfully the first time. To reproduce this, I added the new node to inventory file and reran the ansible playbook. However, I did not see the new node join the cluster. I will close this issue once I am able to successfully add a node to an existing cluster. Does that make sense?

[dougbtv]

@verizonold -- I think that's relative only to kube-ansible repository. Not multus (also, feel free to open the issue there. that case isn't covered by kube-ansible / hasn't been a consideration, feel free to add the feature, and even better if you can make a proposal for changes necessary to support it)