Skip to content

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

@victorming666

Description

@victorming666

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions