Note: We've migrated older meeting notes to a separate page because we reached the maximum length. To read previous meeting notes from February 2021 to November 2023, click here. Akri Developer calls take place every first Tuesday of the month at 8AM to 9AM PST on Zoom. Anyone is welcome to join this call and participate. Please abide by Akri's Code of Conduct. The meetings are recorded and published afterwards on the Deis Labs YouTube Channel. If you would like to propose an agenda item, add a comment to the Agenda section under the specific date. For any other questions or comments, message Yu Jin Kim in the Kubernetes Slack Channel.

https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/co-located-events/cfp/ Dates Salt Lake City, Utah: November 12, 2024 CFP: Due July 14, 2024 Session title options: From Sensors to Servers: Efficient Edge Computing with Akri and WebAssembly Event Driven Edge Data Processing with Akri and WebAssembly Running MQTT Event Driven WebAssembly Applications on the Edge using Akri and SpinKube

The goal of this bug bash is to discover any bugs before Akri creates a new release (v0.13.1). This release contains changes for agent/controller refactoring and directly using kube-rs client structure in the agent. Please leave a comment in the scenario outcomes section with the scenario's you tested and whether it was successful. If you find issues, please create an issue on Akri's GitHub and comment it in the discovered issues section. As always, feel free to post any questions on Akri's Slack. Background Akri is an Open Source project that automates the discovery and usage of IoT devices around Kubernetes clusters on the Edge. Akri can automatically deploy user-provided workloads to the discovered devices. It handles device appearance and disappearance, allowing device deployments to expand and contract and enabling high resource utilization. Setting Up an Environment

The goal of this bug bash is to discover any bugs before Akri creates a new release (v0.13.1). This release contains changes for agent refactory and directly using kube-rs client structure in the agent. Please leave a comment in the scenario outcomes section with the scenario's you tested and whether it was successful. If you find issues, please create an issue on Akri's GitHub and comment it in the discovered issues section. As always, feel free to post any questions on Akri's Slack. Background Akri is an Open Source project that automates the discovery and usage of IoT devices around Kubernetes clusters on the Edge. Akri can automatically deploy user-provided workloads to the discovered devices. It handles device appearance and disappearance, allowing device deployments to expand and contract and enabling high resource utilization. Setting Up an Environment

Akri Developer calls take place every first Tuesday of the month at 8AM to 9AM PST on Zoom. Anyone is welcome to join this call and participate. Please abide by Akri's Code of Conduct. The meetings are recorded and published afterwards on the Deis Labs YouTube Channel. If you would like to propose an agenda item, add a comment to the Agenda section under the specific date. For any other questions or comments, message Yu Jin Kim or Kate Goldenring in the Kubernetes Slack Channel. November 14th Assignments

Speakers: Andrew Gracey and Yu Jin Kim https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/program/cfp/#submit-your-talk Dates Paris: March 19 - 22, 2024 CFP: Due Nov 26, 2023 Session title: [ ] Improving usability at the edge by porting parts of Akri to WebAssembly

https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/program/cfp/#submit-your-talk Dates Paris: March 19 - 22, 2024 CFP: Due Nov 26, 2023 Session title: Bridge your IoT leaf devices to local clusters with ease using Akri and Dynamic Resource Allocation Description

The goal of this bug bash is to discover any bugs before Akri creates a new release. This release contains major changes like configuration-level resource support and improvement of Onvif discovery handler for uuid filtering and authenticated access. Please leave a comment in the scenario outcomes section with the scenario's you tested and whether it was successful. If you find issues, please create an issue on Akri's GitHub and comment it in the discovered issues section. As always, feel free to post any questions on Akri's Slack. Background Akri is an Open Source project that automates the discovery and usage of IoT devices around Kubernetes clusters on the Edge. Akri can automatically deploy user-provided workloads to the discovered devices. It handles device appearance and disappearance, allowing device deployments to expand and contract and enabling high resource utilization. Setting Up an Environment

REQUIREMENTS: 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.

OFFICIAL 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

This document will walk through how to perform a firmware upgrade of an IP camera with Akri. Specifically, it will help you use open source tools to create a mock ONVIF compliant IP camera that has support for the UpgradeSystemFirmware ONVIF Device Management Handle and start an upgrade service that will "upgrade" the camera. The demo will have the following flow: Install Akri with an ONVIF firmware upgrade Configuration Discovery Handler/ Agent discovers camera and creates an Instance CR Controller deploys firmware upgrade broker Broker calls the UpgradeSystemFirmware endpoint on the camera Camera calls its “upgrade service” Upgrade service restarts camera with incremented firmware version

Check Clones and Visitors to Akri Github: https://github.com/project-akri/akri/graphs/traffic Check Forks: https://github.com/project-akri/akri/network/members Check Stars: https://github.com/project-akri/akri/stargazers Check Watch: https://github.com/project-akri/akri/watchers Check Pulls: https://github.com/orgs/project-akri/packages Stars over Time: https://star-history.com/#project-akri/akri&Date CNCF Dev Stats (monitor engagement and more): https://akri.devstats.cncf.io/d/8/dashboards?orgId=1&refresh=15m Slack Members: https://kubernetes.slack.com/archives/C01D9L7QE8Z

Running list of recordings of conference talks and presentations about Akri for reference for folks interested in consuming Akri content in a non-documentation form. Listed from most to least recent in date. Please comment or add any others. Date Title, Link Host Event Content April 18, 2023 Can You Keep a Secret? Securely Interacting with Edge Devices in Kubernetes Cloud Native Kubernetes on Edge Day Europe 2023

Currently, Akri is a pre-release project. The following are some tasks that should be completed for Akri to be production ready. ONGOING: Enable Akri's discovery handlers to authenticate with devices before marking them as discovered. This requires a credentials solution with identity mapping (device to certificate). Enable providing Akri brokers (customer workloads deployed by Akri) appropriate credentials for authenticating with devices. Currently, Akri's OPC UA demo uses Kubernetes secrets COMPLETED: Ensure Akri's Helm templates use the most restrictive settings rather than defaults, using Akri's Snyk report for guidance. Akri maintainers have access to the CNCF Akri Snyk account. For example, explicitly setting securityContext.allowPrivilegeEscalation to false. ONGOING: Investigate and conduct a size reduction of Akri containers. Most Akri binaries are < 25MB; however, the containers can be > 140 MB. There is bloat that can be removed as confirmed by this Issue's investigation Performance testing and stress testing to know Akri's limits and have a benchmark for a v1. Nice to have: Prune Akri's dependencies. This includes being explicit about which features of each crate are used. https://github.com/project-akri/akri/issues/237 Making Akri Feature Full

The goal of this bug bash is to discover any bugs before Akri creates a new release. This release contains the following major changes: Installs crictl directly in the Agent Enable applying multiple Configurations that use the same Discovery Handler Job Brokers (breaking) Please leave a comment in the scenario outcomes section with the scenario's you tested and whether it was successful. If you find issues, please create an issue on Akri's GitHub and comment it in the discovered issues section. As always, feel free to post any questions on Akri's Slack.

The goal of this bug bash is to discover any bugs before Akri creates a new release. This release contains the following major changes: Enable mounting connectivity information for multiple devices/instances in a pod Grouping of udev devices based on parent/child relation Added support for devicespec usage for udev Mount udev devpath in Akri brokers Other release notes: Updated OPC UA demo with OPC PLC containers

If your talk is selected, the abstract title you choose will be the title shown in the conference schedule, often what attendees use as a starting point to determine if they will be interested in the talk. Choose your title carefully - make sure that it accurately describes what your talk will cover. Be sure your title complies with the The Linux Foundation's Inclusive Language Initiative. Please use title case when inputting your title here. (75 Character Max) Can You Keep a Secret? Securely Interacting with Edge Devices In Kubernetes Abstract: Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include and what the presentation will cover. Do not be vague. Be sure your abstract complies with the Linux Foundation's Inclusive Language Initiative. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points ), and write in the third person (use your name instead of “I”). Remember that this description is what will make an attendee decide whether your session would be a good fit for them. Be sure to provide enough information to help attendees make the right choice. Be clear and concise. This description is also one of two primary factors the Program Committee will use to measure the strength and relevance of the presentation, making your abstract strong is essential. The presentation selection process is very competitive, with many proposals rejected. A well-written, thoughtful, and enticing abstract will greatly increase the possibility of the proposal being accepted. (1300 character Max)

Intro Secret Store CSI Driver Drawbacks: Doesn't have data encrypted at rest by itself

Directory of links for maintainers Fun fact: Akri means "edge" in Greek and stands for A Kubernetes Resource Interface Documentation Site (docs.akri.sh) (serves main branch of docs folder in docs repo using GitBooks). This is the first link that can be shared with someone interested in Akri Docs repository Proposals folder: for proposing new features or Discovery Handler. Essentially enhancement documentation that does not need to be seen by general Akri audience (docs.akri.sh) nor can be captured in an issue (needs to be more formalized) Akri's HackMD can be used for brainstorming, quick notes/lists (like this), and other community efforts and notes that do not need to be a part of Akri's documentation site nor is a proposal. GitHub Workflows directory (aka Pipelines)

This note delineates the step-by-step process of creating a new release of Akri on GitHub Test latest supported versions, and update workflow to test the newly supported versions: https://github.com/deislabs/akri/pull/317/commits a. Then update tests to use latest K8s versions Test latest rust version and update workflow: https://github.com/deislabs/akri/pull/318rustup toolchain install stable # switch to using installed latest toolchain (for example 1.51.0) rustup default 1.51.0 # confirm version cargo --version # test build