Keadm Join Error

[liyongxian]

Keadm Join Error

[luomengY]

What I want to express is that the optimization in kubeedge1.16 does not require the installation of CNI plugins when joining edge nodes in keadm. After adding edge nodes, if the pod of the edge application uses a container network, CNI plugins need to be installed again.

[SherlockShemol]

Same problem here.

My problem is kube-proxy-hqjt4 and weave-net-l6z4g cni plugin are both assigned to edge side.

At edge side,

Mar 04 22:24:56 myarch edgecore[985246]: E0304 22:24:56.340679  985246 kubelet.go:2361] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPl
uginNotReady message:Network plugin returns error: cni plugin not initialized"
Mar 04 22:24:56 myarch edgecore[985246]: E0304 22:24:56.623836  985246 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-proxy\" w
ith ImagePullBackOff: \"Back-off pulling image \\\"registry.k8s.io/kube-proxy:v1.28.3\\\"\"" pod="kube-system/kube-proxy-hqjt4" podUID=9e3f7ac1-fd37-4bca-b23b-bad7ae336cc3

kube-proxy image can't be properly pulled. I'm trying to figure it out.

[liyongxian]

Same problem here.

My problem is kube-proxy-hqjt4 and weave-net-l6z4g cni plugin are both assigned to edge side.

At edge side,

Mar 04 22:24:56 myarch edgecore[985246]: E0304 22:24:56.340679  985246 kubelet.go:2361] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPl
uginNotReady message:Network plugin returns error: cni plugin not initialized"
Mar 04 22:24:56 myarch edgecore[985246]: E0304 22:24:56.623836  985246 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-proxy\" w
ith ImagePullBackOff: \"Back-off pulling image \\\"registry.k8s.io/kube-proxy:v1.28.3\\\"\"" pod="kube-system/kube-proxy-hqjt4" podUID=9e3f7ac1-fd37-4bca-b23b-bad7ae336cc3

kube-proxy image can't be properly pulled. I'm trying to figure it out.

EdgeNode Does not Deploy Kube-proxy and Cloud CNI, DaemonSet OF kube-proxy and weave-net Add nodeAffinity:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: node-role.kubernetes.io/edge
operator: DoesNotExist

[SherlockShemol]

Same problem here.
My problem is kube-proxy-hqjt4 and weave-net-l6z4g cni plugin are both assigned to edge side.
At edge side,

Mar 04 22:24:56 myarch edgecore[985246]: E0304 22:24:56.340679  985246 kubelet.go:2361] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPl
uginNotReady message:Network plugin returns error: cni plugin not initialized"
Mar 04 22:24:56 myarch edgecore[985246]: E0304 22:24:56.623836  985246 pod_workers.go:965] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-proxy\" w
ith ImagePullBackOff: \"Back-off pulling image \\\"registry.k8s.io/kube-proxy:v1.28.3\\\"\"" pod="kube-system/kube-proxy-hqjt4" podUID=9e3f7ac1-fd37-4bca-b23b-bad7ae336cc3

kube-proxy image can't be properly pulled. I'm trying to figure it out.

EdgeNode Does not Deploy Kube-proxy and Cloud CNI, DaemonSet OF kube-proxy and weave-net Add nodeAffinity: affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: node-role.kubernetes.io/edge operator: DoesNotExist

抱歉没太明白你的意思，你指的是解决方案还是你遇到的问题？

[liyongxian]

你遇到的问题。Kubeedge节点是不需要部署kube-proxy和cni的。

[SherlockShemol]

你遇到的问题。Kubeedge节点是不需要部署kube-proxy和cni的。

那请问云端和边缘端是如何通信的呢？

[wbc6080]

Could you help take a look at this problem? I remember that in v1.16 we have decoupled the dependence on the cni plug-in during installation, but it seems that the cni plug-in is still required here. @luomengY

[luomengY]

Could you help take a look at this problem? I remember that in v1.16 we have decoupled the dependence on the cni plug-in during installation, but it seems that the cni plug-in is still required here. @luomengY

The optimization of kubedge1.16.0 is that there is no need to install CNI plugins when joining keadm, but after joining an edge node, the application pod of the edge node still needs to install CNI plugins when using container networks. The log of this issue should be caused by not installing CNI plugins.

[luomengY]

和边缘端是如何通信的呢？

However, when deploying edge nodes with keadm join, there is no need to install CNI plugins in advance. If the application runs on an edge node using a container network, CNI plugins need to be installed after keadm join.

[SherlockShemol]

和边缘端是如何通信的呢？

However, when deploying edge nodes with keadm join, there is no need to install CNI plugins in advance. If the application runs on an edge node using a container network, CNI plugins need to be installed after keadm join.

I didn't install CNI plugin in advance at first.But I came across a bug Network plugin returns error: cni plugin not initialized which result in Not Ready state of my edge node.So I install CNI plugin.
My keadm version is v1.16.0 too.

version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.0", GitCommit:"0114a3e44ddeeff747af370ba58c3ef892400bf7", GitTreeState:"clean", BuildDate:"2024-01-23T02:26:43Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/amd64"}

[luomengY]

I didn't install CNI plugin in advance at first.But I came across a bug Network plugin returns error: cni plugin not initialized which result in Not Ready state of my edge node.So I install CNI plugin.
My keadm version is v1.16.0 too.

The edge node has been successfully deployed, and the application pod on the edge node uses container networks, so CNI plugins need to be installed. Are you still reporting an error after installing CNI plugins?

[SherlockShemol]

I didn't install CNI plugin in advance at first.But I came across a bug Network plugin returns error: cni plugin not initialized which result in Not Ready state of my edge node.So I install CNI plugin.
My keadm version is v1.16.0 too.

The edge node has been successfully deployed, and the application pod on the edge node uses container networks, so CNI plugins need to be installed. Are you still reporting an error after installing CNI plugins?

What I want to express is that the optimization in kubeedge1.16 does not require the installation of CNI plugins when joining edge nodes in keadm. After adding edge nodes, if the pod of the edge application uses a container network, CNI plugins need to be installed again.我想表达的是，kubeedge1.16 中的优化并不要求在 keadm 中加入边缘节点时安装 CNI 插件。添加边缘节点后，如果边缘应用的 pod 使用容器网络，则需要重新安装 CNI 插件。

Yes I get you and thank you for your work and explanation.
Another problem is here.kube-proxy image can't be properly pulled. I am going to change the repository at cloudside to see if it works.Now I'm participating in a school internship. I won't know the result until I return to school in the evening.

[luomengY]

Usually, if kube-proxy cannot be run on edge nodes, it may result in a failure to restart edgecore:

（https://kubeedge.io/docs/setup/install-with-keadm）
Adopting edgemesh at edge nodes（ https://github.com/kubeedge/kubeedge/blob/master/docs/proposals/edgemesh-design.md ）Forward traffic as SVC.

[SherlockShemol]

Usually, if kube-proxy cannot be run on edge nodes, it may result in a failure to restart edgecore: （https://kubeedge.io/docs/setup/install-with-keadm） Adopting edgemesh at edge nodes（ https://github.com/kubeedge/kubeedge/blob/master/docs/proposals/edgemesh-design.md ）Forward traffic as SVC.

Finally edgemesh is deployed on both cloud and edge side.The cloud side is in a Ready state. Thank you for your help!

[SherlockShemol]

Usually, if kube-proxy cannot be run on edge nodes, it may result in a failure to restart edgecore:通常，如果无法在边缘节点上运行 kube-proxy，可能会导致无法重启 edgecore： （https://kubeedge.io/docs/setup/install-with-keadm）（https://kubeedge.io/docs/setup/install-with-keadm) Adopting edgemesh at edge nodes（ https://github.com/kubeedge/kubeedge/blob/master/docs/proposals/edgemesh-design.md ）Forward traffic as SVC.在边缘节点采用 edgemesh（ https://github.com/kubeedge/kubeedge/blob/master/docs/proposals/edgemesh-design.md ）作为 SVC 转发流量。

And there is another question.
Just install edgemesh is enough, there is no need to install CNI plugin,right?

[luomengY]

Finally edgemesh is deployed on both cloud and edge side.The cloud side is in a Ready state. Thank you for your help!

Before edgemesh 1.15.0, edgemesh could only support traffic proxies at the SVC level. However, in edgemesh 1.15.0, it already supports container network features, that is, edge node CNI features. You can refer to the documentation in edgemesh 1.15.0 to deploy the new version（ https://mp.weixin.qq.com/s/KogjCv6hB9UAdG7rDVsb3w ）It should be possible to use edgemesh as a CNI plugin at edge nodes.

[SherlockShemol]

0,

Thank you!

[liyongxian]

What I want to express is that the optimization in kubeedge1.16 does not require the installation of CNI plugins when joining edge nodes in keadm. After adding edge nodes, if the pod of the edge application uses a container network, CNI plugins need to be installed again.

Thanks for your reply.
How to deploy cni-plugins on edgenode?
On Cloud,I use Calico.

Thanks.

[luomengY]

What I want to express is that the optimization in kubeedge1.16 does not require the installation of CNI plugins when joining edge nodes in keadm. After adding edge nodes, if the pod of the edge application uses a container network, CNI plugins need to be installed again.

Thanks for your reply. How to deploy cni-plugins on edgenode? On Cloud,I use Calico.

Thanks.

https://release-1-15.docs.kubeedge.io/docs/setup/prerequisites/runtime

[vikarnazbl]

Facing the same issue. Using helm, edgmesh and spiderpool is getting installed but spiderpool-agent pods are going into crashloopbackoff on the edge nodes. kubectl logs output doesn't show any error msg. Is it due to CNI? How to use edgemesh as CNI?