cncf
/
toc
mirror of https://github.com/cncf/toc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
toc/projects/kubeedge/kubeedge-incubation-proposa...

7.0 KiB
Raw Permalink Blame History

KubeEdge proposal for CNCF Incubation

Table of Contents

Background

KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. It's built upon Kubernetes and provides fundamental infrastructure support for network, application deployment and metadata synchronization between cloud and edge.

It aims to resolve three major challenges for edge computing: network reliability and bandwidth limit between cloud and edge, resource constraint at edge, highly distributed and heterogeneous device managements.

KubeEdge provides:

  1. Seamless Cloud-Edge Communication for both metadata and data
  2. Edge Autonomy: Autonomous operation of Edge even when disconnected from cloud.
  3. Low Resource Requirement: KubeEdge can work in constrained resource situations (low memory, low bandwidth, low compute)
  4. Simplified Device Communication: Easy communication between applications and devices for IOT and Industrial Internet of Things (IIoT)

KubeEdge was accepted as a CNCF Sandbox project on Mar 18, 2019.

Continuous Momentum

  • Least Release: v1.3
  • Num of Contributors: 30 => 300+
  • Github Stars: 400+ => 2500+
  • Github Forks: 100+ => 600+
  • Contributing member organizations: 1 => 25+
  • Maintainers (Approvers): 7 (1 company) => 14 (5 companies)
  • Notable improvements since sandbox include:
    • Added Device Management framework to simplify edge application development.
    • Provided Bluetooth and Modbus protocol support for Industrial Internet of Things (IIoT)
    • Introduced EdgeMesh to simplify service communication between edge nodes
    • More container runtime integration supports: containerd, cri-o, kata containers
    • Added high availability of cloud component CloudCore
    • Added CSI integration support on the Edge
    • Support fetching edge pods' logs in the cloud

Alignment with Cloud Native

KubeEdge falls in the scope of CNCF Runtime SIG.

KubeEdge targets on:

  • Building an open edge computing platform with cloud native technologies
  • Helping users extending their business architecture, applications, services, etc. from cloud to edge in same experience
  • Implementing extensible cloud-edge architecture based on Kubernetes
  • Integration with CNCF projects, including (but not limited to) containerd, cri-o, Prometheus, Envoy, etc.
  • Seamless development, deployment and execution of complex workloads at edge with optimized resources

Incubation State Requirements

  1. Document that it is being used successfully in production by at least three independent end users which, in the TOC's judgement, are of adequate quality and scope.

We have the list of public adopters in the repo, some notable users include here:

  • Raisecom, is using KubeEdge to manage AI inferencing applications on the edge to help improve industrial manufacturing safety and efficiency.
  • WoCloud, is using to offer a commercial hosted edge computing service.
  • Xinghai IoT, is using KubeEdge in its smart campus platform.
  • KubeSphere, is using to offer an open source on-prem edge computing service in its container platform.
  • HUAWEI CLOUD, is using to offer a commercial hosted edge computing service.
  • User A (awaiting confirmation to publish name), is using KubeEdge in its highway electronic tolling system.
  • User B (awaiting confirmation to publish name), is using KubeEdge in its Mine Brain solution and served 1000+ coal mines.

There are a few other adopters we are waiting for confirmation to publish name.

  1. Have a healthy number of committers. A committer is defined as someone with the commit bit; i.e., someone who can accept contributions to some or all of the project.

We have 14 approvers, from 5 different companies, including Arm, China Unicom, Huawei, infoblox.com, inovex.de. See OWNERS files under KubeEdge repositories for details.

  1. Demonstrate a substantial ongoing flow of commits and merged contributions.

We are seeing a constant stream of improvements and features from the maintainers and community. See the stats here:

  1. A clear versioning scheme.

KubeEdge follows the semantic versioning spec, and now is under every 3 months release cadence.

We have releases documented at: https://github.com/kubeedge/kubeedge

The latest 4 releases are:

  1. Roadmap

We have a lot of plans for future development, and major items in our roadmap are:

  • Support edge pod metrics collection in the cloud and integrate with Prometheus.
  • Gateway based cross subnet communication on the edge.
  • Support edge-cloud communication using EdgeMesh.
  • Improve edge device management extensibility, support to define/integrate custom device protocol.
  • Decentralized Security for applications on the edge.