Ranganath, Sunku <sunku.ranganath@...>
toggle quoted messageShow quoted text
An important aspect about FabEdge, that I understood, is that it establishes IPSec tunnels between Edge nodes and the cloud.
Leveraging multiple CNIs in a Kubernetes cluster is not an uncommon practice (example
Did you get the info you are looking for?
From: cncf-tag-network@... <cncf-tag-network@...>
On Behalf Of Zhipeng Huang
Sent: Sunday, January 30, 2022 11:58 AM
To: Liz Rice <liz@...>
Cc: Wangzefeng (Kevin) <wangzefeng@...>; cncf-tag-network@...; CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-tag-network] [cncf-toc] Clarification from KubeEdge Community
Just came across the documentation by chance and stumped upon the edgemesh dependency information, 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@...
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.