awesome-repositories.com
Blog
MCP
awesome-repositories.com

Entdecke die besten Open-Source-Repositories mit KI-gestützter Suche.

EntdeckenKuratierte SuchenOpen-Source-AlternativenSelf-hosted SoftwareBlogSitemap
ProjektÜber unsRanking-MethodikPresseMCP-Server
RechtlichesDatenschutzAGB
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
kubeedge avatar

kubeedge/kubeedge

0
View on GitHub↗
7,487 Stars·1,953 Forks·Go·Apache-2.0·5 Aufrufekubeedge.io↗

Kubeedge

KubeEdge is a distributed edge computing framework that extends Kubernetes to manage containerized workloads and hardware devices at the edge. It functions as a Kubernetes edge orchestration system, allowing the deployment and management of applications across distributed edge nodes using native Kubernetes APIs and workflows.

The project distinguishes itself through a specialized focus on IoT integration and node autonomy. It employs digital-twin state modeling to represent physical hardware devices as virtual objects, utilizing an MQTT-based messaging bus for communication with heterogeneous devices. To ensure operational stability during network instability or cloud disconnections, it implements local metadata caching and state persistence, allowing edge nodes to maintain local application operations independently.

The framework provides a comprehensive set of capabilities covering cloud-edge networking via WebSocket and QUIC protocols, distributed device management, and container lifecycle orchestration. It further includes tools for remote pod debugging, centralized node status reporting, and the management of storage volumes and resource reclamation at the edge.

Features

  • Edge - Functions as a distributed orchestration system that synchronizes cluster state and manages pods on remote edge hosts.
  • Cloud-Edge Networking - Establishes secure bidirectional communication between central controllers and remote hosts over WebSocket and QUIC protocols.
  • Environment Synchronizers - Synchronizes resource updates and device status changes between cloud and edge environments to ensure parity.
  • Edge-to-Cloud Synchronization - Provides mechanisms for replicating resource states and metadata between edge devices and centralized cloud storage.
  • Resource Synchronizers - Caches configuration maps and secrets locally on edge nodes to ensure operational stability during network partitions.
  • Local Metadata Stores - Uses lightweight local metadata stores to persist resource configurations and enable autonomous operation.
  • Autonomous Metadata Synchronization - Manages object metadata in local databases to ensure edge nodes remain operational independently of the cloud.
  • Local Persistence - Implements local metadata caching and state persistence to ensure edge nodes remain autonomous during cloud disconnections.
  • Cluster Node Management - Implements tools for managing the operational parameters and lifecycle of nodes within the edge cluster.
  • Container Orchestrators - Automates the deployment, scaling, and management of containerized applications across distributed edge clusters.
  • Distributed Container Orchestration - Provides lifecycle management of containers across distributed multi-node clusters at the edge.
  • Kubernetes Edge Platforms - Provides a Kubernetes distribution optimized for resource-constrained devices and distributed edge computing scenarios.
  • Pod Lifecycle Management - Manages the full lifecycle of containerized workloads at the edge using CRI-compliant runtimes.
  • Edge Node Autonomy - Maintains local application operations and resource state on remote nodes during network instability or cloud disconnections.
  • Edge Orchestration Layers - Implements a distributed management layer for deploying and updating applications across remote or isolated edge infrastructure.
  • Local Autonomy Assurance - Maintains local application operations and node stability when the network connection to the cloud is unstable or offline.
  • Cluster State Synchronization - Synchronizes configurations and resource state between the cloud management plane and edge nodes.
  • Resource Lifecycle Coordination - Coordinates the distribution of configuration maps and the lifecycle of pods across distributed edge locations.
  • Workload Orchestration - Manages the application lifecycles and resource configurations for containerized workloads deployed at the edge.
  • Device Attribute Management - Updates and manages configuration and state attributes of IoT devices based on cloud instructions.
  • Attribute State Tracking - Updates and stores current status and custom attributes of devices for application retrieval.
  • Device-Node Mapping - Binds edge devices to specific edge nodes and maintains membership lists to track associations.
  • Digital Twin Querying - Retrieves digital twin data and membership details for devices associated with an edge node.
  • Digital Twin State Management - Implements digital-twin state modeling to represent physical hardware devices as virtual objects for decoupled metadata synchronization.
  • Digital Twin State Modeling - Implements digital-twin modeling to represent physical hardware as virtual objects for state synchronization.
  • Digital Twin Synchronization - Synchronizes digital twin state and attributes between the edge and the cloud to ensure consistent device representations.
  • Distributed Device Management - Tracks device attributes and memberships across a fleet of edge nodes to synchronize state with a central cloud.
  • Hardware Device Integration - Tracks device metadata and status through custom resource definitions to integrate hardware devices into the orchestration layer.
  • IoT Device Management Platforms - Integrates heterogeneous hardware devices using digital-twin state modeling and MQTT for cloud-edge communication.
  • IoT Device Metadata Synchronization - Synchronizes device properties and status between cloud and edge environments using templates for device models and instances.
  • Cloud-Edge Communication Bridges - Provides a networking layer using WebSocket and QUIC protocols to maintain stable bidirectional data flow between cloud and edge.
  • Device State Synchronizers - Ensures local hardware state consistency with cloud controllers after network events using device state synchronizers.
  • Network Reliability - Ensures reliable delivery of messages and resource updates over unstable networks using persistent connections.
  • Resource State Synchronization - Ensures resource alignment and consistency between the cloud management plane and distributed edge clusters.
  • Configuration Propagators - Propagates resource updates and configuration changes from the central cloud API to remote edge nodes.
  • Device Connectivity Tracking - Updates and stores the current state and last-online timestamp of edge devices and propagates changes to event buses.
  • Edge-to-Cloud Message Routing - Routes messages from edge nodes to cloud controllers via WebSocket or QUIC protocols.
  • Fleet - Enables simultaneous modification of configuration settings across multiple edge nodes to ensure consistency across the fleet.
  • Remote Configuration Synchronization - Synchronizes and caches configuration maps and secrets from a remote provider for local edge access.
  • Edge Resource Management - Processes the creation, update, and deletion of containerized objects by coordinating messages between the cloud and edge runtime.
  • Edge Runtime Deployment - Deploys necessary cloud and edge runtime components to connect the orchestration layer with edge hosts.
  • High Availability Clusters - Configures orchestration components in redundant setups to ensure fault tolerance and high availability.
  • Multi-Component Upgrades - Coordinates the upgrade of multiple distributed components across the cloud and edge environments.
  • Industrial IoT Platforms - Provides backend infrastructure for managing and processing data from industrial sensor networks using digital twins and MQTT.
  • Edge Service Interfacing - Communicates with sensors and edge services through dedicated MQTT and HTTP channels.
  • IoT Device Server Implementation - Implements an IoT device server that manages communication between a network controller and local cluster logic.
  • MQTT Messaging Integrations - Facilitates communication between edge components and devices using the MQTT protocol.
  • Bi-Directional Traffic Tunneling - Establishes bidirectional data paths between central controllers and remote hosts using WebSocket and QUIC.
  • Publish-Subscribe Messaging - Provides pub-sub messaging capabilities for resource-constrained devices to communicate with edge components.
  • Edge Traffic Management - Provides service discovery and traffic proxying to manage networking for applications in edge environments.
  • QUIC Implementations - Utilizes the QUIC transport protocol to maintain stable data transfer over high-latency edge networks.
  • Pub-Sub Messaging - Employs an MQTT-based pub-sub messaging architecture to decouple heterogeneous edge devices from the orchestration layer.
  • Cluster API Simulation - Provides local API endpoints on edge nodes to simulate cluster APIs for local applications.
  • Secret Caching - Stores configuration maps and secrets in a local database to reduce latency and support offline access.
  • Centralized Monitoring Platforms - Collects health metrics from edge nodes and pods and forwards them to a central cloud controller.
  • Distributed Metric Collection - Gathers operational and performance data from a distributed network of edge nodes.
  • Endpoint Status Reporting - Generates aggregated reports on the operational status and health of edge nodes and pods for the central API server.
  • HTTP Health Probes - Provides liveness and readiness probes to monitor the health of containerized workloads at the edge.
  • Pod State Monitoring - Reports the execution state and health of running pods from the edge node to the cloud.
  • WebSocket State Synchronization - Maintains persistent WebSocket connections to synchronize resource states and metadata between cloud and edge.
  • Edge Computing - Framework for extending Kubernetes to edge computing.
  • Infrastructure and Operations - Extends orchestration to edge computing devices.

Star-Verlauf

Star-Verlauf für kubeedge/kubeedgeStar-Verlauf für kubeedge/kubeedge

KI-Suche

Entdecke weitere awesome Repositories

Beschreibe in einfachen Worten, was du brauchst — die KI bewertet tausende kuratierte Open-Source-Projekte nach Relevanz.

Start searching with AI

Open-Source-Alternativen zu Kubeedge

Ähnliche Open-Source-Projekte, sortiert nach der Anzahl der gemeinsamen Funktionen mit Kubeedge.
  • blynk-technologies/blynk-libraryAvatar von Blynk-Technologies

    Blynk-Technologies/blynk-library

    3,971Auf GitHub ansehen↗

    Blynk is an embedded device framework and IoT cloud connectivity library designed to establish secure, bi-directional communication between microcontrollers and a remote management platform. It provides the core identity of an IoT device management tool, enabling the synchronization of device states, remote hardware control, and the mapping of hardware data to cloud-based interfaces. The project distinguishes itself through a virtual-pin system that decouples cloud communication from physical pins, allowing for hardware-independent data exchange. It also supports advanced architectural offloa

    C++arduinocellularembedded
    Auf GitHub ansehen↗3,971
  • dgiot/dgiotAvatar von dgiot

    dgiot/dgiot

    4,824Auf GitHub ansehen↗

    dgiot is an open source industrial IoT platform and gateway designed to integrate diverse industrial communication protocols and standardize data exchange between hardware and software. It serves as a device management system and low-code orchestrator capable of monitoring millions of simultaneous connections. The platform utilizes a visual environment for digital twin modeling to map physical hardware to standardized digital representations. It includes a visual rule engine for processing device data to trigger automated actions and alerts, alongside a low-code configuration pipeline for gen

    Erlangdgiotindustrial-iotiot
    Auf GitHub ansehen↗4,824
  • docker-archive-public/docker.labsAvatar von docker-archive-public

    docker-archive-public/docker.labs

    11,904Auf GitHub ansehen↗

    This project is a comprehensive collection of tutorials and guided laboratories designed to teach containerization, networking, and security using Docker. It serves as a learning path for building portable images and executing isolated processes. The materials provide specific guides for managing container clusters and scaling services through Docker Swarm and overlay networks. It includes a security handbook for implementing image scanning and secret management, as well as laboratories dedicated to modernizing legacy applications by wrapping older software installers into containers. The co

    PHPcontainersdockerdocker-compose
    Auf GitHub ansehen↗11,904
  • domoticz/domoticzAvatar von domoticz

    domoticz/domoticz

    3,778Auf GitHub ansehen↗

    Domoticz is a home automation platform and multi-protocol IoT orchestrator designed for controlling smart home devices and automating routines. It functions as an event-driven automation engine and a centralized system for managing connected sensors and hardware across Linux, Windows, and Raspberry Pi. The system acts as a Zigbee and Z-Wave controller and an MQTT IoT gateway, bridging disparate hardware ecosystems through a flexible plugin system. This allows for the unification of various communication standards into a single management interface. The platform covers broad capabilities incl

    C++cppdomoticzdzvents
    Auf GitHub ansehen↗3,778
Alle 30 Alternativen zu Kubeedge anzeigen→

Häufig gestellte Fragen

Was macht kubeedge/kubeedge?

KubeEdge is a distributed edge computing framework that extends Kubernetes to manage containerized workloads and hardware devices at the edge. It functions as a Kubernetes edge orchestration system, allowing the deployment and management of applications across distributed edge nodes using native Kubernetes APIs and workflows.

Was sind die Hauptfunktionen von kubeedge/kubeedge?

Die Hauptfunktionen von kubeedge/kubeedge sind: Edge, Cloud-Edge Networking, Environment Synchronizers, Edge-to-Cloud Synchronization, Resource Synchronizers, Local Metadata Stores, Autonomous Metadata Synchronization, Local Persistence.

Welche Open-Source-Alternativen gibt es zu kubeedge/kubeedge?

Open-Source-Alternativen zu kubeedge/kubeedge sind unter anderem: blynk-technologies/blynk-library — Blynk is an embedded device framework and IoT cloud connectivity library designed to establish secure, bi-directional… domoticz/domoticz — Domoticz is a home automation platform and multi-protocol IoT orchestrator designed for controlling smart home devices… kubernetes-sigs/descheduler — Descheduler is a Kubernetes workload rebalancer and pod eviction manager designed to optimize resource distribution… dgiot/dgiot — dgiot is an open source industrial IoT platform and gateway designed to integrate diverse industrial communication… docker-archive-public/docker.labs — This project is a comprehensive collection of tutorials and guided laboratories designed to teach containerization,… chillzhuang/springblade — SpringBlade is a development framework and platform designed for building multi-tenant SaaS applications. It provides…