v0.7.31 Release Notes

OPC UA Connector

Breaking Changes
- BrokerAuthentication configuration syntax updated.
- Added "settings" suffix to each method configuration object name.
- x509Credentials renamed to x509Settings.
New Features
- Support for configuration via Azure portal.
Fixes
- Fixed issue preventing BrokerAuthentication deployment via ARM.
- Fixed bugs in BrokerListener configuration preventing certain advanced cert-manager properties.
General
- New default service name: aio-broker.
- New pod names: aio-broker-frontend-0 and aio-broker-backend-0.
- New default broker listener port: 18883 for AIO internal communication to vacate common user ports 1883 and 8883, avoiding conflicts or misconfiguration.
- New Kubernetes service account audience: aio-internal for default broker authentication, used by other AIO components.
- Performance improvements.

Breaking Changes
- CRD and ARM API; fields renamed
Integration
- Schema registry for reserialization and transformation.
New Features
- Configuration via IoT Operations Experience portal.
- Sending data to Fabric OneLake, ADLSv2, and Azure Data Explorer.
- Use MQTT message properties in map transformations.
- Get last-known-value in transformations.
- Compatibility with Cloud Events attributes.
- Auto-determine system-assigned managed identity audience.
- Use user-assigned managed identity with dataflow endpoints via workload identity federation.
Default Settings
- Auto-generated DataflowEndpoint (named default) with each AIO deployment.
- Default DataflowProfile renamed to default.
Fixes
- Deploying dataflows via ARM.
- Clarified supported authentication methods for each endpoint type.
- Authentication configuration moved inside endpoint-type-specific settings (e.g. mqttSettings).
- Scaling up instance count beyond 1.
- Default values for MQTT endpoint types to built-in MQTT broker.
General
- Performance improvements.

Breaking Changes
- Removed Akri agent and UDF discovery support where Akri instance akrii CRs are created for discovered OPC UA assets.
- Discovered Asset and Discovered Asset Endpoint Profile using mPRC (the end-to-end flow is not yet supported).
General
- Automatic asset discovery is NOT being deprecated - it will return with a new and improved version in the next refresh.
- Note: You will still see Akri deployed on your cluster as a part of Azure IoT Operations.

New Feature
- Ability to upgrade has been implemented in this release - Customers will be able to upgrade to the next version of the AIO arc extension without needing to redeploy everything.
- Integration of Cert manager and Trust Manager for setting up secure communications internally among pods and between pods and external endpoints.

New Features
- AIO Install/Deployment based on customer need.
  - "Test Setting": Simpler deployment for testing purposes.
  - "Secure Setting": Deployment for production use cases, includes support for User Assigned Managed Identity and Secret management.
- Ability to select an existing schema registry or create a new one from the AIO Install wizard.
- Optional dependencies deployment
  - MQTT: listeners, authentication and authorization
Breaking Changes
- CLI command changes in portal automation screen for Edge Storage Accelerator (ESA), Schema registry, Workload identity federation, and az iot ops init vs create.

New Features
- Dataflows - A dataflow can subscribe to an MQTT topic and forward the messages to an event hub in your Azure Event Hubs namespace.
- Integrate with Schema Registry RP and use Schema Registry ARG.
- Dataflow Endpoints - A dataflow endpoint is the connection point for the dataflow.
- Dataflow Endpoints – access token AKV and Azure Secret Store integration.
Breaking Changes
- Asset endpoint profile – username/password AKV and Azure Secret Store integration.

New Features
- Schema Registry
  - Synchronization of message schemas between cloud and edge.
  - Ability for OPC UA Connector to store message schemas in Schema Registry.
  - Ability for Dataflows to consume message schemas in dataflows.
  - Ability for upload user-generated message schemas in Operations Experience.
  - Ability to author Dataflows with schemas in Operations experience.
- Asset and Asset Endpoint Profile
  - Added reference to message schemas.
  - Ability to define dataset.
  - Add ability to set MQTT topic and retain flag on a per asset, and per dataset basis.
Breaking changes
- Changes to Asset + Asset Endpoint Profile ARM & CR field names and structure.

New Features
- Deployment of Azure IoT Operations are now broken into two phases:
  - Deploy AIO dependencies via init
  - Creation of AIO instance via create
- Updated delete to delete AIO instances by default created by create, append --include-deps flag to undo init.
- Added identity command group for general management of workload identity.
- Added secretsync command group for secret sync configurations of Azure IoT Operations instance.
- Added data flow to check command.

New Features
- Support of User Assigned Managed Identity for northbound connections.

New Features
- Ability to automatically sync secrets from Azure Key Vault down to edge using Operations Studio.
- Ability to use secrets for southbound and northbound connections.
- Ability to delete synced secrets from edge.
- Ability to add new synced secrets to edge.

This release has been validated on the latest September update of AKS Edge Essentials (version 1.8.202.0).