Skip to content

Commit 9b9385d

Browse files
committed
update akri overview
1 parent 63b28f8 commit 9b9385d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-operations/discover-manage-assets/overview-akri.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36,17 +36,17 @@ IoT leaf devices present the following challenges, They:
3636
To address the challenge of integrating non-Kubernetes IoT leaf devices, the Akri services have several core capabilities:
3737

3838
### Connector deployment and lifecycle management
39+
3940
Akri services include the Akri operator which allows connector workloads to be deployed dynamically when certain types of devices or assets are discovered/configured, provides automatic access to Azure IoT Operations resources and endpoints (like Devices and Assets), deploys connector workloads to the right nodes based on discovery information like node affinity, and more.
4041

4142
### Asset detection
43+
4244
Akri services also include the Azure Device Registry (ADR) service component, which work with the connectors that have asset detection capabilities. These connectors enable the metadata and preconfigured datasets, events, etc. to be onboarded with ease through known device endpoints. Akri ADR service creates the detected Assets as custom resources which are picked up by the operations experience UI so that as an OT, you can seamlessly view and onboard the detected assets into the Azure Device Registry.
4345

4446
### Device discovery
4547

4648
Akri services deployments can include fixed-network discovery handlers. Discovery handlers enable assets from known network endpoints to find leaf devices as they appear on device interfaces or local subnets. Examples of network endpoints include OPC UA servers at a fixed IP address, and network scanning discovery handlers. This is not yet supported in this release.
4749

48-
Akri services deployments can include fixed-network discovery handlers. Discovery handlers enable assets from known network endpoints to find leaf devices as they appear on device interfaces or local subnets. Examples of network endpoints include OPC UA servers at a fixed IP address, and network scanning discovery handlers. This is not yet supported in this release.
49-
5050

5151
### Compatibility with Kubernetes
5252

@@ -61,7 +61,7 @@ The following table shows the connectors currently available in Azure IoT Operat
6161
| Connector for OPC UA | Yes | Yes |
6262
| Connector for ONVIF | No | Yes |
6363
| Media connector | Yes | No |
64-
| HTTP connector | No | No |
64+
| REST/HTTP connector | No | No |
6565

6666
The media connector supports discovery of cameras and other media devices that use the ONVIF protocol.
6767

0 commit comments

Comments
 (0)