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
| —– BEGIN LICENSE —– | |
| Mifeng User | |
| Single User License | |
| EA7E-1184812 | |
| C0DAA9CD 6BE825B5 FF935692 1750523A | |
| EDF59D3F A3BD6C96 F8D33866 3F1CCCEA | |
| 1C25BE4D 25B1C4CC 5110C20E 5246CC42 | |
| D232C83B C99CCC42 0E32890C B6CBF018 | |
| B1D4C178 2F9DDB16 ABAA74E5 95304BEF | |
| 9D0CCFA9 8AF8F8E2 1E0A955E 4771A576 |
| #!/bin/bash | |
| # A simple script to backup an organization's GitHub repositories. | |
| #------------------------------------------------------------------------------- | |
| # NOTES: | |
| #------------------------------------------------------------------------------- | |
| # * Under the heading "CONFIG" below you'll find a number of configuration | |
| # parameters that must be personalized for your GitHub account and org. | |
| # Replace the `<CHANGE-ME>` strings with the value described in the comments | |
| # (or overwrite those values at run-time by providing environment variables). |