1. Cncf-Toc
  2. Topics

Clarification from KubeEdge Community

Zhipeng Huang
 

Just came across the documentation by chance and stumped upon the edgemesh dependency information[0], pretty straight forward to me that it is not tightly coupled with KubeEdge in any way. 


On Wed, Jan 26, 2022, 1:10 AM Liz Rice <liz@...> wrote:
Thanks for these comments

Looking at the README for FabEdge I am somewhat confused about the statement that "FabEdge is a CNI" (where I'm taking that to be shorthand for "Kubernetes CNI Plugin" i.e. a component that provides the Container Networking Interface to a Kubernetes cluster). From the README my understanding is that FabEdge is providing edge connectivity, but not connectivity for Kubernetes pods within the cluster? It needs to be used alongside a CNI (examples of Calico and Flannel are given), so I'm not sure how it can itself be a CNI?  

Maybe the answer is that FabEdge is providing edge connectivity, but that there are other "control plane" aspects of edge computing that it does not cover? And that the KubeEdge project provides these control plane aspects, tightly coupled with edge connectivity coming from the EdgeMesh component? Please, do correct me if this is not the correct understanding. 

TAG Network folks, what are your thoughts here? Please advise. 

Thanks,
Liz


On Mon, Jan 24, 2022 at 8:47 AM Kevin Wang via lists.cncf.io <wangzefeng=huawei.com@...> wrote:
Thank you.

Kevin
--
KubeEdge | Volcano | Kubernetes | CNCF | LF Edge

Haotao Geng
 

There are two parts:  the 1st one is the k8s cluster in the cloud, in which some traditional CNI is used, such as Flannel/Calico, FabEdge is NOT to replace it, but to add edge connectivity on-top of it.  For the 2nd part, the k8s remote nodes in the edge,  in which FabEdge provides both the connectivity for k8s pods via the existing bridge CNI/host-local plugins and the edge connectivity.  Is it a CNI or not?  If not,  how to describe it more accurately?  I appreciate your advice. 

Haotao Geng
FabEdge

Liz Rice
 

Thanks for these comments

Looking at the README for FabEdge I am somewhat confused about the statement that "FabEdge is a CNI" (where I'm taking that to be shorthand for "Kubernetes CNI Plugin" i.e. a component that provides the Container Networking Interface to a Kubernetes cluster). From the README my understanding is that FabEdge is providing edge connectivity, but not connectivity for Kubernetes pods within the cluster? It needs to be used alongside a CNI (examples of Calico and Flannel are given), so I'm not sure how it can itself be a CNI?  

Maybe the answer is that FabEdge is providing edge connectivity, but that there are other "control plane" aspects of edge computing that it does not cover? And that the KubeEdge project provides these control plane aspects, tightly coupled with edge connectivity coming from the EdgeMesh component? Please, do correct me if this is not the correct understanding. 

TAG Network folks, what are your thoughts here? Please advise. 

Thanks,
Liz


On Mon, Jan 24, 2022 at 8:47 AM Kevin Wang via lists.cncf.io <wangzefeng=huawei.com@...> wrote:
Thank you.

Kevin
--
KubeEdge | Volcano | Kubernetes | CNCF | LF Edge

Kevin Wang
 

Thank you.

Kevin
--
KubeEdge | Volcano | Kubernetes | CNCF | LF Edge

Haotao Geng
 

Hello TOC and broader community and Kevin, 

I do apologize for any incorrect wording in the slides and I do apologize for any misunderstanding it caused.  

I respond and clarify it as below:

---------------------------------------------

1. As an open community, we fully welcome fabedge and any other projects to consider being part of the KubeEdge community.

Response:  absolutely YES. 

2. KubeEdge can work together with any standard CNIs. And EdgeMesh is a tool running together with 3rd party CNIs to simplify cross subnet communications, not to replace them.

Response:  absolutely YES.  KubeEdge can work with any standard CNI, while FabEdge is a CNI.

3. As an open source project, we don't prevent any Apache 2.0-compliant usage by any user. We are grateful for the recognition KubeEdge has received in the industry, and we would be happy if users including SuperEdge, OpenYurt, and others incorporate some pieces of KubeEdge.

Response:  absolutely YES. 

---------------------------------------------------- 

BTW, I removed the incorrect comment in my slides.  Pls. let me know if anything else I need to do. 

Haotao Geng

FabEdge

Kevin Wang
 

Hello TOC and broader community,

 

Recently we saw some incorrect information about the KubeEdge community in a fabedge presentation to the TAG network:

 

 

 

 

I would like to correct the understanding :

 

1. As an open community, we fully welcome fabedge and any other projects to consider being part of the KubeEdge community.

2. KubeEdge can work together with any standard CNIs. And EdgeMesh is a tool running together with 3rd party CNIs to simplify cross subnet communications, not to replace them.

3. As an open source project, we don't prevent any Apache 2.0-compliant usage by any user. We are grateful for the recognition KubeEdge has received in the industry, and we would be happy if users including SuperEdge, OpenYurt, and others incorporate some pieces of KubeEdge.

 

 

If you have any further questions or would like to discuss anything regarding KubeEdge, please just let us know.

 

 

Thanks,

Kevin Wang on behalf of the KubeEdge Maintainers


--
KubeEdge | Volcano | Kubernetes | CNCF | LF Edge

1 - 6 of 6