I saw that the resulting generated file in the filesystemwith multus 4.0.2 looks quite different:
the structure is different,top level elements are "cniVersion", "name" and "plugins".
The "kubeconfig" entry is auto-created under "plugins". If has always the value passed via command line argument "multus-kubeconfig-file-host" (or it's default), regardless of the value in the configmap
"plugins/capabilities" seems also to be auto-generated, regardless of the value in the configmap
So my question is, is the config file in the yaml still in an up-to-date format? Are the enties like "capabilities" or "kubeconfig" required (or even used)? If not, it would make sense to update the example config.
Hello,
I have been playing around a bit with multus. The example configuration in https://github.com/k8snetworkplumbingwg/multus-cni/blob/master/deployments/multus-daemonset.yml looks like that:
I saw that the resulting generated file in the filesystemwith multus 4.0.2 looks quite different:
So my question is, is the config file in the yaml still in an up-to-date format? Are the enties like "capabilities" or "kubeconfig" required (or even used)? If not, it would make sense to update the example config.