// the find
FabEdge/fabedge
Secure Edge Networking Solution Based On Kubernetes
FabEdge extends Kubernetes networking to edge nodes and edge clusters using IPSec tunnels managed by strongSwan. It sits alongside your existing CNI (Calico, Flannel) rather than replacing it — the cloud side keeps whatever it has, and FabEdge handles the cloud-to-edge and edge-to-edge paths. The target audience is teams running KubeEdge, SuperEdge, or OpenYurt who need encrypted connectivity between cloud and edge without hand-rolling VPN configs.
The Operator pattern doing automatic lifecycle management of certs, subnets, and configmaps per edge node is the right call — manual certificate distribution at scale is how edge deployments go wrong. Topology-aware DNS (Fab-DNS) actually routing to the nearest endpoint rather than bouncing traffic across WAN links is a real operational win for IoT latency. The clean separation of concerns between Operator, Connector, and Agent means each component has a narrow failure domain. The test coverage in pkg/operator is thorough — controller tests, allocator tests, store tests — more than most infrastructure projects at this star count.
Strongswan dependency means you're shipping a full IKEv2 daemon in every edge node container, which is heavy for constrained IoT hardware where this would actually be deployed. Multi-cluster support exists but the docs for it are shallow — the design doc references diagrams and the Chinese-only cross-cluster doc, which is a meaningful gap if you're not reading Mandarin. Last release was 1.0.0 with no clear roadmap beyond docs/roadmap.md; CNCF sandbox status with 529 stars and community meetings hosted on Bilibili suggests the primary user base is Chinese enterprises, so if you're outside that ecosystem you may find limited community support when things go wrong. The e2e tests require a real cluster setup and there's no local dev environment story — getting started with contributing is harder than it should be.