The OVS-CNI does not create configuration files in the directory /etc/cni/net.d/

[alasijia666]

I first installed Calico, then installed Multus. Following the instructions at https://github.com/k8snetworkplumbingwg/ovs-cni/blob/main/docs/deployment-on-arbitrary-cluster.md, I installed ovs-cni, which appeared to work initially. However, I did not find the ovs-cni configuration file in /etc/cni/net.d/. This might explain why, after removing Calico, I could not use ovs-cni independently. The issue manifests in CoreDNS remaining stuck in the ContainerCreating state after being restarted. Additionally, I created an ovs.conf based on https://github.com/k8snetworkplumbingwg/ovs-cni/blob/main/docs/cni-plugin.md, which likely contains configuration errors.

coredns error
Normal SandboxChanged 8s (x25 over 34s) kubelet Pod sandbox changed, it will be killed and re-created. Warning FailedCreatePodSandBox 8s (x16 over 25s) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to set up sandbox container "510b12d528352cfe6fb22654dbb8e77f141fb23cec0d4e5556258379955e1627" network for pod "coredns-6f454b4459-4rztm": networkPlugin cni failed to set up pod "coredns-6f454b4459-4rztm_kube-system" network: plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"510b12d528352cfe6fb22654dbb8e77f141fb23cec0d4e5556258379955e1627" Netns:"/proc/953768/ns/net" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=kube-system;K8S_POD_NAME=coredns-6f454b4459-4rztm;K8S_POD_INFRA_CONTAINER_ID=510b12d528352cfe6fb22654dbb8e77f141fb23cec0d4e5556258379955e1627" Path:"" ERRORED: error configuring pod [kube-system/coredns-6f454b4459-4rztm] networking: Multus: [kube-system/coredns-6f454b4459-4rztm/]: failed to get clusterNetwork/defaultNetworks: GetDefaultNetworks: failed to get clusterNetwork /host/etc/cni/net.d/01-ovs.conf in namespace kube-system ': StdinData: {"capabilities":{"bandwidth":true,"portMappings":true},"clusterNetwork":"/host/etc/cni/net.d/01-ovs.conf","cniVersion":"0.3.1","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","runtimeConfig":{"portMappings":[]},"type":"multus-shim"}

01-ovs.conf
`{
"cniVersion": "0.3.1",
"name": "ovs-network",

"plugins": [
{
"container_settings":{"allow_ip_forwarding":false},
"datastore_type":"kubernetes",
"ipam": {
"type": "host-local",
"subnet": "10.244.0.0/16"},
"kubernetes":{"k8s_api_root":"https://10.96.0.1:443"},
"type":"ovs",
"bridge": "br1"
},
"socket_file": "unix:/host/var/run/openvswitch/db.sock",
"link_state_check_retries": 5,
"link_state_check_interval": 1000
]
}
`

[SchSeba]

Hi @alasijia666,

Just a comment here be aware that ovs-cni is not a primary CNI it was develop as a secondary CNI using multus.
this file is for the defalt CNI (that was calico in your case)