kubeedge/edge
KubeEdge Bot 24dc5e625d
Merge pull request #6929 from Priyanshubhartistm/test/servicebus-auth-unit-tests
edge/metaserver: add unit tests for auth package JWT issuer validation
2026-08-04 16:21:26 +08:00
..
cmd servicebus: add transport-layer TLS to embedded HTTP server 2026-07-29 13:18:52 +05:30
hack/memfootprint-test
mocks fix ut for gorm 2026-03-02 10:53:30 +08:00
pkg Merge pull request #6929 from Priyanshubhartistm/test/servicebus-auth-unit-tests 2026-08-04 16:21:26 +08:00
test
README.md

This section contains the source code for KubeEdge edge side components

KubeEdge Edge

At the edge side, there are six major components.

  • EdgeHub: a web socket client responsible for interacting with Cloud Service for the edge computing (like Edge Controller as in the KubeEdge Architecture). This includes syncing cloud-side resource updates to the edge, and reporting edge-side host and device status changes to the cloud.
  • Edged: an agent that runs on edge nodes and manages containerized applications.
  • EventBus: a MQTT client to interact with MQTT servers (mosquitto), offering publish and subscribe capabilities to other components.
  • ServiceBus: a HTTP client to interact with HTTP servers (REST), offering HTTP client capabilities to components of cloud to reach HTTP servers running at edge.
  • DeviceTwin: responsible for storing device status and syncing device status to the cloud. It also provides query interfaces for applications.
  • MetaManager: the message processor between edged and edgehub. It is also responsible for storing/retrieving metadata to/from a lightweight database (SQLite).