0

I'm trying to setup kubedge with cloudcore in EKS (k8s version 1.21.12) and edgecore in an external server. As part of the kubeedge setup, I had to create a node object manually in cloudside which will be labelled as edge node. But when I do the kubectl apply -f node.json, I'm getting the following response:

C:\Users\akhi1\manifest>kubectl apply -f node.json
node/edge-node-01 created

C:\Users\akhi1\manifest>kubectl get nodes
NAME                                               STATUS   ROLES    AGE     VERSION
ip-xx-xx-xxx-213.ap-southeast-1.compute.internal   Ready    <none>   3h48m   v1.21.12-eks-xxxx   << this node was already in my eks cluster

As you can see, I'm not able see the newly created node 'edge-node-01' in the list. On checking the kube events, I got the following:

C:\Users\akhi1\manifests>kubectl get events
LAST SEEN   TYPE     REASON         OBJECT               MESSAGE
13m         Normal   DeletingNode   node/edge-node-01    Deleting node edge-node-01 because it does not exist in the cloud provider

For manually node registration, I followed this doc: https://kubernetes.io/docs/concepts/architecture/nodes/#manual-node-administration

My node.json would look like this:

{
  "kind": "Node",
  "apiVersion": "v1",
  "metadata": {
    "name": "edge-node-01",
    "labels": {
      "name": "my-first-k8s-edge-node"
    }
  }
}

I have also checked, node restriction and admission controller but couldn't find anything related to it.

Please let me know why, eks is blocking me to create a node object that doesn't have an underlying ec2 attached.

Thanks in advance, Akhil

akhi1
  • 1,322
  • 1
  • 16
  • 25

0 Answers0