Multus 3.0 Design Proposal

[edsealing]

Multus v3.0 has implemented a lot of changes to conform with the Kubernetes SIG standards. v3.0 is not compatible with previous versions of Multus. EDCOP multi-networking will need to be overhauled to implement v3.0.

• Research new version implementation details
• Proposal: CNI binary implementation of Multus
• Proposal: Modifications required to implement Calico with Multus v3.0

Research needed:

• According to Multus v3.0 release notes, Multus can be "launched as a DaemonSet". Currently, we implement the binary as an RPM and deploy it on each node. Does the new version place the binary on each node via DaemonSet?

• How is CNI-chaining implemented in Multus v3.0?

• Previous iterations required us to heavily modify the default Calico yaml files and adapt for Multus v1.2. How is the new process defined for implementing a network under Multus?