kubeedge VS osm-edge

Introduction：KubeEdge is an open source edge computing platform. Based on the native container arrangement and scheduling ability of Kubernetes (K8s), it realizes the functions of cloud edge collaboration, computing sinking, massive edge device management, edge autonomy, etc. It is completely open, scalable, easy to develop and maintain, and supports offline mode and cross-platform. GitHub：https://github.com/kubeedgeKubeEdge: https://kubeedge.ioArchitecture diagram of KubeEdge: https://kubeedge.io/en/docs/kubeedge/#architecture Features:

It’s sounding like you want to run a kube cluster on the edge, but required to run Windows workloads and hoping to fit the solution into a single physical machine (correct me if I’m wrong). I don’t have a good answer for you, as normally for edge you would consider something like KubeEdge, but it doesn’t appear they support Windows nodes at this time.

Kubeedge docs are light on self-justification... How does https://github.com/kubeedge/kubeedge differ from https://github.com/virtual-kubelet/virtual-kubelet or just running a regular kubelet on that edge machine?

Flomesh open source service mesh osm-edge is based on an implementation of the SMI (Service Mesh Interface) standard. SMI defines specifications for traffic identification, access control, telemetry, and management. In the previous article Kubernetes: Multi-cluster communication with Flomesh Service Mesh we covered the background, motivations, and goals of Kubernetes multi-cluster and part 2 Kubernetes: Multi-cluster communication with Flomesh Service Mesh (Demo) we demonstrated a detailed demo of how to use FSM in a multi-cluster environment and how to schedule policies for traffics.

This article will focus on the second approach, which allows support for fine-grained access control on who can access services within the service mesh. This feature is newly added and available in release 1.2.0 osm-edge v1.2.0.

system=$(uname -s | tr [:upper:] [:lower:]) arch=$(dpkg --print-architecture) release=v1.1.1 curl -L https://github.com/flomesh-io/osm-edge/releases/download/${release}/osm-edge-${release}-${system}-${arch}.tar.gz | tar -vxzf - . /${system}-${arch}/osm version cp . /${system}-${arch}/osm /usr/local/bin/

osm-edge is built on top of Open Service Mesh (OSM) v1.1.0 codebase and is a lightweight service mesh for resource-sensitive cloud environments and edge computing scenarios. It uses osm as the control plane and Pipy as the data plane and features high performance, low resources, simplicity, ease of use, scalability, and compatibility (x86/arm64 support).

The evolution of Kubernetes to the edge side solves the difficulties of edge computing to a certain extent, especially against fragility; while the development of service mesh to the edge side focuses on network issues in edge computing, against network fragility, as well as providing basic network support for distributed, such as fault migration. In practice, container platforms, as today's de facto quasi-standard means of application delivery, are rapidly evolving to the edge side, with a large number of releases targeting edge features, such as k3s; but service mesh, as an important network extension for container platforms, are not quickly keeping up with this trend. It is currently difficult for users to find service mesh for edge computing scenarios, so we started the osm-edge an open source project with several important considerations and goals, namely