Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

why edgemesh-agent can't deployed on the edge node? #576

Open
victorming666 opened this issue Dec 9, 2024 · 4 comments
Open

why edgemesh-agent can't deployed on the edge node? #576

victorming666 opened this issue Dec 9, 2024 · 4 comments

Comments

@victorming666
Copy link

Kubernetes Versions:
Client Version: v1.24.16
Kustomize Version: v4.5.4
Server Version: v1.24.16
Kubedge version:
v1.13.0
EdgeMesh version:
v1.14.0

kubectl get nodes:
NAME STATUS ROLES AGE VERSION
aiot-edgenode-1 Ready agent,edge 3d1h v1.23.15-kubeedge-v1.13.0
aiot-master Ready control-plane,master 5d v1.24.16
aiot-worker Ready 4d23h v1.24.16

kubectl get all -n kubeedge -o wide:
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
pod/cloudcore-5c9c57545f-g7xb5 1/1 Running 0 126m 192.168.100.251 aiot-worker
pod/edgemesh-agent-khbn7 1/1 Running 0 49m 192.168.100.251 aiot-worker

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR
service/cloudcore ClusterIP 10.111.6.11 10000/TCP,10001/TCP,10002/TCP,10003/TCP,10004/TCP 126m k8s-app=kubeedge,kubeedge=cloudcore

NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE CONTAINERS IMAGES SELECTOR
daemonset.apps/edgemesh-agent 1 1 1 1 1 117m edgemesh-agent kubeedge/edgemesh-agent:v1.14.0 k8s-app=kubeedge,kubeedge=edgemesh-agent

NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
deployment.apps/cloudcore 1/1 1 1 126m cloudcore kubeedge/cloudcore:v1.13.0 k8s-app=kubeedge,kubeedge=cloudcore

NAME DESIRED CURRENT READY AGE CONTAINERS IMAGES SELECTOR
replicaset.apps/cloudcore-5c9c57545f 1 1 1 126m cloudcore kubeedge/cloudcore:v1.13.0 k8s-app=kubeedge,kubeedge=cloudcore,pod-template-hash=5c9c57545f

@victorming666
Copy link
Author

kubectl get node aiot-edgenode-1 --show-labels
NAME STATUS ROLES AGE VERSION LABELS
aiot-edgenode-1 Ready agent,edge 3d1h v1.23.15-kubeedge-v1.13.0 beta.kubernetes.io/arch=arm64,beta.kubernetes.io/os=linux,gpu=false,kubernetes.io/arch=arm64,kubernetes.io/hostname=aiot-edgenode-1,kubernetes.io/os=linux,node-role.kubernetes.io/agent=,node-role.kubernetes.io/edge=,nvidia.com/gpu.deploy.operands=false

Edgecore logs on edge node "aiot-edgenode-1":
Dec 09 16:06:02 aiot-edgenode-1 edgecore[30961]: E1209 16:06:02.211789 30961 edged.go:254] resType is not pod or configmap or secret or volume: resType is endpoints
Dec 09 16:06:07 aiot-edgenode-1 edgecore[30961]: E1209 16:06:07.211792 30961 edged.go:254] resType is not pod or configmap or secret or volume: resType is endpoints
Dec 09 16:06:12 aiot-edgenode-1 edgecore[30961]: E1209 16:06:12.212061 30961 edged.go:254] resType is not pod or configmap or secret or volume: resType is endpoints
Dec 09 16:06:17 aiot-edgenode-1 edgecore[30961]: E1209 16:06:17.217551 30961 edged.go:254] resType is not pod or configmap or secret or volume: resType is endpoints
Dec 09 16:06:22 aiot-edgenode-1 edgecore[30961]: E1209 16:06:22.215981 30961 edged.go:254] resType is not pod or configmap or secret or volume: resType is endpoints
Dec 09 16:06:27 aiot-edgenode-1 edgecore[30961]: E1209 16:06:27.219435 30961 edged.go:254] resType is not pod or configmap or secret or volume: resType is endpoints

@victorming666
Copy link
Author

victorming666 commented Dec 10, 2024

I found this was caused as the edge node 'aiot-edgenode-1' has a taint which blocks the edgemesh-agent pod deployed on the edge node. I removed this taint and the pod could be deployed on the edge node successfully.
But now, there is another issue as below:
image
the edgecore service on the edge node keeps on logging:
Dec 10 09:13:03 aiot-edgenode-1 edgecore[30961]: E1210 09:13:03.882752 30961 edged.go:254] resType is not pod or configmap or secret or volume: resType is endpoints
Anybody can figure out the reason?

@victorming666
Copy link
Author

Error when testing the HTTP Forwarding testcase:
kubectl exec -it alpine-test -n default -- sh
/ # curl hostname-svc:12345
curl: (7) Failed to connect to hostname-svc port 12345 after 3051 ms: Host is unreachable

@victorming666
Copy link
Author

At last, I redeployed kubeedge+edgemesh. The test passed:

~/software/aiot/edgemesh$ kubectl exec -it alpine-test -- sh
/ # curl hostname-svc:12345
hostname-edge-f5f6569d-vg9qv
/ # curl hostname-svc:12345
hostname-edge-f5f6569d-vg9qv

And the logs of edgemesh-agent at edge node:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant