kubeedge/mappers-go

KubeEdge Device Mappers written in go

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kubeedge/mappers-go has 50+ stars and 70+ forks on GitHub, is written in Go, and was last pushed on Oct 31, 2024. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on October 15th, 2026
Created on December 23rd, 2020
Open Issues & Pull Requests: 55 (+0)
GitHub issues: Enabled
Number of forks: 70
Total Stargazers: 52 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.8 hours
Mean response time: 16.0 days
90th percentile: 32.0 days
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 484 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

mappers-go is a collection of device mappers written in Go that enable KubeEdge to connect to edge devices using various protocols.

The project solves the problem of integrating diverse edge devices into KubeEdge clusters by providing protocol-specific mappers and a framework for building custom ones. It includes ready-made implementations for Modbus, Bluetooth, ONVIF, and OPC UA protocols. For protocols not covered by existing mappers, the mapper-sdk-go framework abstracts the connection to KubeEdge, device property and status management, and data conversion, allowing developers to focus on implementing only the protocol-specific driver interface for their device type.

Teams should adopt this tool if they need to connect edge devices to KubeEdge and their devices use one of the supported protocols, or if they need to build a custom mapper for a proprietary or less common protocol. The project is suited for edge computing deployments where devices must be managed and monitored through a Kubernetes-based control plane. The mapper-sdk-go framework significantly reduces development effort by handling boilerplate integration work, making it practical to create mappers for custom protocols without reimplementing core KubeEdge connectivity logic.

The project maintains active development with regular updates to both the protocol implementations and the SDK framework. Contributions flow steadily across multiple mapper implementations and the core SDK, indicating ongoing refinement of existing functionality. The codebase shows consistent attention to the mapper-sdk-go framework, suggesting the maintainers view it as a critical component for extensibility. Documentation is maintained in multiple languages, reflecting an effort to serve a geographically distributed user base.