By default, K3S will run with flannel as the CNI and use custom directories to store CNI plugin binaries and config files(You can inspect the kubelet args K3S uses via journalctl -u k3s|grep cni-conf-dir).
So you need to configure that properly When deploying Multus CNI.
For example given the official Multus manifests in https://github.com/intel/multus-cni/blob/36f2fd64e0965e639a0f1d17ab754f0130951aba/images/multus-daemonset.yml, the following changes are needed:
volumes:
- name: cni
| source <(kubectl completion bash) | |
| __start_kubectl_cust() | |
| { | |
| local cur prev words cword | |
| declare -A flaghash 2>/dev/null || : | |
| if declare -F _init_completion >/dev/null 2>&1; then | |
| _init_completion -s || return | |
| else | |
| __kubectl_init_completion -n "=" || return | |
| fi |
| """ | |
| Copies all keys from the source Redis host to the destination Redis host. | |
| Useful to migrate Redis instances where commands like SLAVEOF and MIGRATE are | |
| restricted (e.g. on Amazon ElastiCache). | |
| The script scans through the keyspace of the given database number and uses | |
| a pipeline of DUMP and RESTORE commands to migrate the keys. | |
| Requires Redis 2.8.0 or higher. |