Skip to content

Commit ae1c0d2

Browse files
authored
Merge pull request #290582 from dominicbetts/release-aio-ga-akri-fix
AIO [GA]: Minor Akri updates
2 parents 5ef7610 + f44853d commit ae1c0d2

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/iot-operations/deploy-iot-ops/howto-manage-update-uninstall.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ In general, Azure IoT Operations uses the Azure Arc platform to provide a hybrid
139139

140140
However, you can also manage the components of Azure IoT Operations using YAML Kubernetes deployment manifests. This means you can use tools like `kubectl` to manage some components of Azure IoT Operations. This feature is in preview and has some limitations:
141141

142-
- Only some components support using Kubernetes deployment manifests. These components are the [MQTT broker](../manage-mqtt-broker/overview-broker.md) and [dataflows](../connect-to-cloud/overview-dataflow.md). Other components like the connector for OPC UA and Akri don't support this feature.
142+
- Only some components support using Kubernetes deployment manifests. These components are the [MQTT broker](../manage-mqtt-broker/overview-broker.md) and [dataflows](../connect-to-cloud/overview-dataflow.md). Other components like the connector for OPC UA and Akri services don't support this feature.
143143
- Unless Azure IoT Operations is [deployed with resource sync enabled using `az iot ops create --enable-rsync`](/cli/azure/iot/ops#az-iot-ops-create), changes made to the resources using Kubernetes deployment manifests are not synced to Azure. To learn more about resource sync, see [Resource sync](/azure/azure-arc/data/resource-sync).
144144
- Even if resource sync is enabled, brand new resources created using Kubernetes deployment manifests are not synced to Azure. Only changes to existing resources are synced.
145145

articles/iot-operations/overview-iot-operations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,11 +75,11 @@ Azure IoT Operations uses the Azure Device Registry to store information about l
7575

7676
## Automatic asset discovery
7777

78-
Automatic asset discovery using Akri services, Azure Device Registry, the connector for OPC UA, the connection for ONVIF (preview), and the media connector (preview) is available in the current version of Azure IoT Operations. Currently, there are no user configurable scenarios for Akri in the operations experience web UI.
78+
Automatic asset discovery using Akri services, Azure Device Registry, the connector for OPC UA, the connection for ONVIF (preview), and the media connector (preview) is available in the current version of Azure IoT Operations. Currently, there are no user configurable scenarios for Akri services in the operations experience web UI for automatic asset discovery.
7979

8080
To learn more, see the [release notes](https://github.com/Azure/azure-iot-operations/releases) for the current version.
8181

82-
If you're using a previous preview version of Azure IoT Operations, you can find the Akri documentation on the [previous versions site](/previous-versions/azure/iot-operations/discover-manage-assets/overview-akri).
82+
If you're using a previous preview version of Azure IoT Operations, you can find the Akri services documentation on the [previous versions site](/previous-versions/azure/iot-operations/discover-manage-assets/overview-akri).
8383

8484
## Publish and subscribe with MQTT
8585

0 commit comments

Comments
 (0)