Interworking with 0.4.0 and 0.3.1 (or previous) CNI version

[s1061123]

Since CNI version 0.4.0, CHECK command is introduced. If user configures multus config as follows, then CHECK command will be sent to delegate CNI, flannel and we get error message from kubelet.

What should we do for that...

[fedora@kube-master1 ~]$ sudo cat /etc/cni/net.d/00-multus.conf  | jq
{
  "cniVersion": "0.4.0",
  "name": "multus-cni-network",
  "type": "multus",
  "capabilities": {
    "portMappings": true
  },
  "logLevel": "debug",
  "logFile": "/tmp/multus.log",
  "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig",
  "delegates": [
    {
      "name": "cbr0",
      "cniVersion": "0.3.1",
      "plugins": [
        {
          "type": "flannel",
          "delegate": {
            "hairpinMode": true,
            "isDefaultGateway": true
          }
        },
        {
          "type": "portmap",
          "capabilities": {
            "portMappings": true
          }
        }
      ]
    }
  ]
}

  Warning  FailedCreatePodSandBox  2s    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get network status for pod sandbox k8s_fedora-nonet_default_888e2e8f-4551-46d2-858a-87e5bbeb31e7_0(457da3c23a303d35c61737e78f5a7a2996f881516ab3dcd4f84382943928b42c): delegateCheck: error invoking ConflistCheck - "cbr0": conflistCheck: error in getting result from CheckNetworkList: configuration version "0.3.1" does not support the CHECK command

[dougbtv]

We should not accept 0.3.1 or earlier in the case of 0.4.0 at the top level config. May need to be implemented in entrypoint.

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.