Master CNI file flag option isn't working for thin plugin about multus-cni

[jhoblitt]

I ran into this as well upgrading from (ancient) 3.4 -> 4.0.2. With

     - name: kube-multus
        image: ghcr.io/k8snetworkplumbingwg/multus-cni:v4.0.2
        command: ["/thin_entrypoint"]
        args:
        - "--multus-conf-file=auto"
        - "--multus-autoconfig-dir=/host/etc/cni/net.d"
        - "--cni-conf-dir=/host/etc/cni/net.d"
        - "--multus-master-cni-file-name=10-canal.conflist"

It keeps sucking in 00-multus.conf on every restart:

pretty printed

{
  "cniVersion": "0.3.1",
  "name": "multus-cni-network",
  "type": "multus",
  "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig",
  "delegates": [
    {
      "cniVersion": "0.3.1",
      "delegates": [
        {
          "cniVersion": "0.3.1",
          "delegates": [
            {
              "cniVersion": "0.3.1",
              "delegates": [
                {
                  "cniVersion": "0.3.1",
                  "delegates": [
                    {
                      "cniVersion": "0.3.1",
                      "name": "k8s-pod-network",
                      "plugins": [
                        {
                          "datastore_type": "kubernetes",
                          "ipam": {
                            "subnet": "usePodCidr",
                            "type": "host-local"
                          },
                          "kubernetes": {
                            "kubeconfig": "/etc/cni/net.d/calico-kubeconfig"
                          },
                          "log_file_path": "/var/log/calico/cni/cni.log",
                          "log_level": "info",
                          "mtu": 1450,
                          "nodename": "kueyen01",
                          "policy": {
                            "type": "k8s"
                          },
                          "type": "calico"
                        },
                        {
                          "capabilities": {
                            "portMappings": true
                          },
                          "snat": true,
                          "type": "portmap"
                        },
                        {
                          "capabilities": {
                            "bandwidth": true
                          },
                          "type": "bandwidth"
                        }
                      ]
                    }
                  ],
                  "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig",
                  "name": "multus-cni-network",
                  "type": "multus"
                }
              ],
              "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig",
              "name": "multus-cni-network",
              "type": "multus"
            }
          ],
          "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig",
          "name": "multus-cni-network",
          "type": "multus"
        }
      ],
      "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig",
      "name": "multus-cni-network",
      "type": "multus"
    }
  ]
}

It seems like the default output file should be filtered out of the input cni config file list.

[dougbtv]

Thanks for the heads up. When we deprecated the entrypoint.sh it looks like this parameter might've been missed.