# Akri Bug Bash - June 2025
###### tags: `Bug Bash`

The goal of this bug bash is to discover any bugs before Akri creates a new release (v0.13.15). This release contains bug fixes, improvements and a reduced image size.

Please leave a comment in the [scenario outcomes](#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](https://github.com/project-akri/akri) and comment it in the [discovered issues](#Discovered-Issues-or-Enhancements) section.

As always, feel free to post any questions on Akri's [Slack](https://kubernetes.slack.com/messages/akri).

## 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 is regularly tested on K3s, MicroK8s, and standard Kubernetes clusters versioned 1.28-1.31 (see [previous release](https://github.com/project-akri/akri/releases) for list of exact versions tested) with Ubuntu 20.04 node. While we only test on these K8s distributions, feel free to try it out on the distribution and Linux OS of your choice. Here are some examples of what you can do:
- Hyper-V Ubuntu 20.04 VM
- Set up Linux VM with cloud provider
- Try out Akri on a managed Kubernetes service

It is recommmended to setup a muli-node cluster as your test environment. The following bug bash scenarios are using 3-node cluster as an example.

## Scenarios  

Choose any of the following scenarios (none are pre-requisite of the others). Make sure to use the **akri-dev chart** (`helm install akri akri-helm-charts/akri-dev`) when installing Akri with Helm. If you have previously installed akri, be sure to run `helm repo update`.

### Scenario A: Device Discovery

Use any of the demos in our docs to test that the device discovery and broker functions are working properly:

- [Debug echo](https://docs.akri.sh/development/debugging)
- [udev](https://docs.akri.sh/demos/usb-camera-demo)
- [OPC UA](https://docs.akri.sh/demos/opc-thermometer-demo)
- [ONVIF](https://docs.akri.sh/demos/onvif-authentication-access)

### Scenario B: nodeSelector for Webhook Configuration

Ensure that installing Akri with the webhook configuration nodeSelector works properly:

helm install akri akri-helm-charts/akri-dev \
  --set useLatestContainers=true \
  --set-string agent.nodeSelectors.worker="true"  \
  --set-string webhookConfiguration.nodeSelectors.worker="true"

### Scenario C: Multi-node setup cleanup

Deploy Akri on a multi-node cluster and then discover devices using one of our demo scenarios in A. Try deleting the Akri instances and ensure that the metadata and finalizers are cleared properly.

### Scenario D: Documentation Walkthrough
It would be great to walk through the documentation with the bug bash and note which changes to docs we would need to make. There are some pending PRs on the documentations as well that go with the release.

## Discovered Issues or Enhancements

## Scenario Outcomes
Please write the environment you used (Kubernetes distro/version and VM), the scenarios you tested, and whether it was a success or had issues.

| Environment | Scenario | Success/Issue |
|--------------|-----------|---------------|
| | | |