[doc] About install.md

[khalid-huang]

In the install.md , root@node1:~# git clone https://github.com/fabedge/fabeedge.git the link of the fabedge is wrong

[khalid-huang]

Do we need to install the calico before kubeedge? Does the calico agent need to be install on the edge node?

[khalid-huang]

How can we know the edgePodCIDR, subnets, ip in the deploy/connector/cm.yaml?

[haotaogeng]

In the install.md , root@node1:~# git clone https://github.com/fabedge/fabeedge.git the link of the fabedge is wrong

sorry, I will update it soon.

[haotaogeng]

Do we need to install the calico before kubeedge? Does the calico agent need to be install on the edge node?

calico is needed in the k8s cluster in cloud, it is not needed on the edge node.

[haotaogeng]

How can we know the edgePodCIDR, subnets, ip in the deploy/connector/cm.yaml?

It is the subnet, from which the ip address for the pod running at the edge nodes are allocated. U can choose one per your env as long as it is not conflicted with the subnet of pod & service in the k8s cluster in the cloud.

[khalid-huang]

Thanks very much.
Do you mean that all the edge nodes will get their own podCIDR from the edgePodCIDR?
And what about ip and subnets in the tunnel.yaml. I do not understand what "ip of connector to terminate tunnels " means? And Do the subnets equalto the kube-apiserver's service-cluster-ip-range?

[khalid-huang]

By the way, does fabedge have any requirements for the node's network? For example, all edge nodes must be able to access each other or in the same lan?

[haotaogeng]

Thanks very much.
Do you mean that all the edge nodes will get their own podCIDR from the edgePodCIDR?

yes

And what about ip and subnets in the tunnel.yaml. I do not understand what "ip of connector to terminate tunnels " means?

it is the ip address, which terminates the tunnel from remote edge nodes to the cloud. And the connector pod runs on a cloud node using host network, so u can use the ip address of this node for it. This is the simplest case. For HA deploy, with more connector instances, we need to use keepalived/vip for it .

And Do the subnets equalto the kube-apiserver's service-cluster-ip-range?

it should contain both service-cluster-ip-range and the ip range for the pods in cloud, which is managed by calico. btw, u can get it using "calicoctl.sh get pool" command.

[haotaogeng]

By the way, does fabedge have any requirements for the node's network? For example, all edge nodes must be able to access each other or in the same lan?

all edge nodes must be able to access the connector at cloud side. If we need one edge node to access the other directly using "community", it also needed for the direct connection between the two edge nodes.

[khalid-huang]

The Calico is need to be installed in the k8s. And the calico is only needed to be install on the cloud. According to the https://docs.projectcalico.org/getting-started/kubernetes/quickstart, I successfully installed calico. But the calico-agent is installed on the edge node too. I do not find how to avoid this. The deployment and the daemonset is created by the calico-opeartor.

I want to avoid this, because it seems that the pod of the edge in fabedge namespace remains in a pending state. I do not know why, so I try to solve the calico problem.

[haotaogeng]

Yes, we need to disable calico-node on edge nodes. Can you update the daemonset?

[khalid-huang]

After I update the daemonset, the daemonset will be rewrited back. I don't know why. How do you disable calico-node on edge nodes?

[haotaogeng]

we use kubespray. To update the ansible templates before deployment.

[khalid-huang]

Could you tell me how to update the ansible templates? I am not familiar with kubespray, and I did not find how to modify it on the offical website. @haotaogeng

[khalid-huang]

@haotaogeng

[haotaogeng]

we'll post some scripts to do this in next week.

[haotaogeng]

a quick-start-guide for the installation of k8s+kubeedge is added. Hope it can help you.

[github-actions]

Stale issue message