k8snetworkplumbingwg / multus-cni

A CNI meta-plugin for multi-homed pods in Kubernetes
Apache License 2.0
2.29k stars 575 forks source link

Failed to create pod sandbox after installing Multus #1223

Closed xutzin closed 5 months ago

xutzin commented 5 months ago

I followed the quick-start guide to install multus

cat ./deployments/multus-daemonset-thick.yml | kubectl apply -f -

After the installation, all pod creation failed even without network annotation

Kubeadm 1.29.1+ Kube-VIP + Flannel 0.24.2 (vxlan)

Warning FailedCreatePodSandBox 4m11s (x108 over 32m) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "37d62803903c18514dc60e3a2f93e5f26164fd1668ac3ff911d0c2ea356abe98": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: '&{ContainerID:37d62803903c18514dc60e3a2f93e5f26164fd1668ac3ff911d0c2ea356abe98 Netns:/var/run/netns/cni-a2a96f79-db3f-e024-bcd8-95afff12b320 IfName:eth0 Args:K8S_POD_UID=e4c60f6c-502b-4bd8-a1f4-b188ab7c9c6e;IgnoreUnknown=1;K8S_POD_NAMESPACE=orqestra;K8S_POD_NAME=conductor-db-7b6c8bb675-fbhgr;K8S_POD_INFRA_CONTAINER_ID=37d62803903c18514dc60e3a2f93e5f26164fd1668ac3ff911d0c2ea356abe98 Path: StdinData:[123 34 99 97 112 97 98 105 108 105 116 105 101 115 34 58 123 34 112 111 114 116 77 97 112 112 105 110 103 115 34 58 116 114 117 101 125 44 34 99 104 114 111 111 116 68 105 114 34 58 34 47 104 111 115 116 114 111 111 116 34 44 34 99 108 117 115 116 101 114 78 101 116 119 111 114 107 34 58 34 47 104 111 115 116 47 101 116 99 47 99 110 105 47 110 101 116 46 100 47 49 48 45 102 108 97 110 110 101 108 46 99 111 110 102 108 105 115 116 34 44 34 99 110 105 67 111 110 102 105 103 68 105 114 34 58 34 47 104 111 115 116 47 101 116 99 47 99 110 105 47 110 101 116 46 100 34 44 34 99 110 105 86 101 114 115 105 111 110 34 58 34 48 46 51 46 49 34 44 34 108 111 103 76 101 118 101 108 34 58 34 118 101 114 98 111 115 101 34 44 34 108 111 103 84 111 83 116 100 101 114 114 34 58 116 114 117 101 44 34 109 117 108 116 117 115 65 117 116 111 99 111 110 102 105 103 68 105 114 34 58 34 47 104 111 115 116 47 101 116 99 47 99 110 105 47 110 101 116 46 100 34 44 34 109 117 108 116 117 115 67 111 110 102 105 103 70 105 108 101 34 58 34 97 117 116 111 34 44 34 110 97 109 101 34 58 34 109 117 108 116 117 115 45 99 110 105 45 110 101 116 119 111 114 107 34 44 34 115 111 99 107 101 116 68 105 114 34 58 34 47 104 111 115 116 47 114 117 110 47 109 117 108 116 117 115 47 34 44 34 116 121 112 101 34 58 34 109 117 108 116 117 115 45 115 104 105 109 34 125]} ContainerID:"37d62803903c18514dc60e3a2f93e5f26164fd1668ac3ff911d0c2ea356abe98" Netns:"/var/run/netns/cni-a2a96f79-db3f-e024-bcd8-95afff12b320" IfName:"eth0" Args:"K8S_POD_UID=e4c60f6c-502b-4bd8-a1f4-b188ab7c9c6e;IgnoreUnknown=1;K8S_POD_NAMESPACE=orqestra;K8S_POD_NAME=conductor-db-7b6c8bb675-fbhgr;K8S_POD_INFRA_CONTAINER_ID=37d62803903c18514dc60e3a2f93e5f26164fd1668ac3ff911d0c2ea356abe98" Path:"" ERRORED: error configuring pod [orqestra/conductor-db-7b6c8bb675-fbhgr] networking: Multus: [orqestra/conductor-db-7b6c8bb675-fbhgr/e4c60f6c-502b-4bd8-a1f4-b188ab7c9c6e]: error waiting for pod: Get "https://10.96.0.1:443/api/v1/namespaces/orqestra/pods/conductor-db-7b6c8bb675-fbhgr?timeout=1m0s": dial tcp 10.96.0.1:443: connect: network is unreachable '

Any advice would be appreciated

xutzin commented 5 months ago

It turns out to be network setting issue