Akri Developer calls take place every first Tuesday of the month at 8AM to 9AM PST on Zoom.
9/21/2023The goal of this bug bash is to discover any bugs before Akri creates a new release. This release contains various bug fixes/improvements and support for configuration-level resources.
9/13/2023REQUIREMENTS: https://github.com/project-akri/akri/issues/614 Background Akri is a Kubernetes Resource Interface that exposes heterogeneous leaf devices (such as IP cameras, OPC UA servers, and USB devices) as resources in a Kubernetes cluster. Akri continually detects nodes that have access to these devices and schedules workloads based on them. Simply put: you name it, Akri finds it, you use it. Why Akri At the edge, there are a variety of sensors, controllers, and MCU class devices that are producing data and performing actions. For Kubernetes to be a viable edge computing solution, these heterogeneous “leaf devices” need to be easily utilized by Kubernetes clusters. However, many of these leaf devices are too small to run Kubernetes themselves. Akri discovers them using common protocols (OPC UA, ONVIF, udev, etc.) and registers them as resources using the device plugin framework. Connectivity isn't a given at the edge, so Akri handles the dynamic appearance and disappearance of leaf devices. Akri's controller automatically brings down Pods that use devices that are no longer online and redeploys them when devices reconnect.
6/13/2023OFFICIAL ROADMAP LIVES HERE: https://docs.akri.sh/community/roadmap Here is a list of our backlog / features we want to implement in the future. Additional Protocol Support MQTT RTSP Zeroconf/mDNS Bluetooth CoAP
6/13/2023