Basic thick plugin installation failed with quickstart instructions.

[dougbtv]

Using quickstart instructions at master... I didn't seem to get a configuration file generated on disk?

Steps that I took...

    3  kubectl create -f flannel.yml 
    4  watch -n1 kubectl get pods
    5  watch -n1 kubectl get pods -A
    6  kubectl get nodes
    7  exit
    8  git clone https://github.com/k8snetworkplumbingwg/multus-cni.git && cd multus-cni
   10  git clone https://github.com/k8snetworkplumbingwg/multus-cni.git && cd multus-cni
   11  cat ./deployments/multus-daemonset-thick.yml | kubectl apply -f -
   12  watch -n1 kubectl get pods -A
   13  sudo su
   14  cat <<EOF | kubectl create -f -
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: bridge-conf
spec:
  config: '{
      "cniVersion": "0.3.0",
      "type": "bridge",
      "bridge": "cnitest0",
      "ipam": {
        "type": "host-local",
        "subnet": "192.168.1.0/24",
        "rangeStart": "192.168.1.200",
        "rangeEnd": "192.168.1.216",
        "routes": [
          { "dst": "0.0.0.0/0" }
        ],
        "gateway": "192.168.1.1"
      }
    }'
EOF

   27  cat <<EOF | kubectl create -f -
apiVersion: v1
kind: Pod
metadata:
  name: samplepod
  annotations:
    k8s.v1.cni.cncf.io/networks: bridge-conf
spec:
  containers:
  - name: samplepod
    command: ["/bin/ash", "-c", "trap : TERM INT; sleep infinity & wait"]
    image: alpine
EOF

   28  kubectl get pods
   ## No interfaces
   29  kubectl exec -it samplepod -- ip a
   30  kubectl describe pod samplepod
   31  sudo su
   32  kubectl get pods
   33  kubectl get pods -A
   34  kubectl describe pod kube-multus-ds-28csc
   35  kubectl describe pod kube-multus-ds-28csc -n kube-system
   36  kubectl logs kube-multus-ds-28csc -n kube-system
   37  ls
   38  sudo su
   ## No 00-multus.conf
   39  ls /etc/cni/net.d

Wondering if something needs to be fixed up for a default install?

[Eoghan1232]

I hit the same issue, although I can see in the logs

Generated MultusCNI config: {"capabilities":{"portMappings":true},"cniVersion":"0.3.1","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","clusterNetwork":"/host/etc/cni/net.d/10-flannel.conflist","type":"multus-shim"}

[Eoghan1232]

manually creating the file fixes my issue, but strange it did not create the file automatically.