Skip to content

Commit 1a0819a

Browse files
jlianjlian
committed
Mark WASM data flow graphs GA; normalize Kubernetes manifest labels
1 parent 73562c7 commit 1a0819a

5 files changed

Lines changed: 41 additions & 46 deletions

File tree

‎articles/iot-operations/connect-to-cloud/howto-configure-opentelemetry-endpoint.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -240,7 +240,7 @@ Deploy the file by running the following Azure CLI command:
240240
az deployment group create --resource-group <RESOURCE_GROUP> --template-file <FILE>.bicep
241241
```
242242

243-
# [Kubernetes](#tab/kubernetes)
243+
# [Kubernetes (preview)](#tab/kubernetes)
244244

245245
Create a Kubernetes manifest `.yaml` file with the following content:
246246

@@ -319,7 +319,7 @@ authentication: {
319319
}
320320
```
321321

322-
# [Kubernetes](#tab/kubernetes)
322+
# [Kubernetes (preview)](#tab/kubernetes)
323323

324324
```yaml
325325
authentication:
@@ -357,7 +357,7 @@ authentication: {
357357
}
358358
```
359359

360-
# [Kubernetes](#tab/kubernetes)
360+
# [Kubernetes (preview)](#tab/kubernetes)
361361

362362
```yaml
363363
authentication:
@@ -394,7 +394,7 @@ authentication: {
394394
}
395395
```
396396

397-
# [Kubernetes](#tab/kubernetes)
397+
# [Kubernetes (preview)](#tab/kubernetes)
398398

399399
```yaml
400400
authentication:
@@ -424,7 +424,7 @@ tls: {
424424
}
425425
```
426426

427-
# [Kubernetes](#tab/kubernetes)
427+
# [Kubernetes (preview)](#tab/kubernetes)
428428

429429
```yaml
430430
tls:
@@ -448,7 +448,7 @@ tls: {
448448
}
449449
```
450450

451-
# [Kubernetes](#tab/kubernetes)
451+
# [Kubernetes (preview)](#tab/kubernetes)
452452

453453
```yaml
454454
tls:
@@ -482,7 +482,7 @@ batching: {
482482
| `latencySeconds` | Maximum time to wait before sending a batch. | 60 seconds |
483483
| `maxMessages` | Maximum number of messages in a batch. | 100000 messages |
484484

485-
# [Kubernetes](#tab/kubernetes)
485+
# [Kubernetes (preview)](#tab/kubernetes)
486486

487487
```yaml
488488
batching:

‎articles/iot-operations/connect-to-cloud/howto-configure-registry-endpoint.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,26 @@
11
---
2-
title: Configure Registry Endpoints in Azure IoT Operations (Preview)
2+
title: Configure registry endpoints in Azure IoT Operations
33
description: Learn how to configure registry endpoints for container registries in Azure IoT Operations data flow graphs.
44
author: sethmanheim
55
ms.author: sethm
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: how-to
9-
ms.date: 08/14/2025
9+
ms.date: 12/17/2025
1010
ai-usage: ai-assisted
1111

1212
#CustomerIntent: As an operator, I want to understand how to configure registry endpoints in Azure IoT Operations so that I can pull WASM modules and graph definitions from container registries.
1313
---
1414

15-
# Configure registry endpoints (preview)
15+
# Configure registry endpoints
1616

1717
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
1818

1919
Data flow graphs use registry endpoints to pull WebAssembly (WASM) modules and graph definitions from container registries. You can configure the endpoint settings, authentication, and other settings to connect to Azure Container Registry (ACR) or other OCI-compatible registries.
2020

2121
## Prerequisites
2222

23-
- An instance of [Azure IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md), version 1.2 preview or later
23+
- An instance of [Azure IoT Operations](../deploy-iot-ops/howto-deploy-iot-operations.md), version 1.2 or later
2424
- Access to a container registry, such as Azure Container Registry
2525

2626
## Registry endpoint overview
@@ -119,7 +119,7 @@ Deploy the Bicep file using Azure CLI:
119119
az deployment group create --resource-group <RESOURCE_GROUP> --template-file <FILE>.bicep
120120
```
121121

122-
# [Kubernetes](#tab/kubernetes)
122+
# [Kubernetes (preview)](#tab/kubernetes)
123123

124124
Create a Kubernetes manifest `.yaml` file with the following content:
125125

@@ -201,7 +201,7 @@ authentication: {
201201
}
202202
```
203203

204-
# [Kubernetes](#tab/kubernetes)
204+
# [Kubernetes (preview)](#tab/kubernetes)
205205

206206
```yaml
207207
authentication:
@@ -258,7 +258,7 @@ authentication: {
258258
}
259259
```
260260

261-
# [Kubernetes](#tab/kubernetes)
261+
# [Kubernetes (preview)](#tab/kubernetes)
262262

263263
```yaml
264264
authentication:
@@ -323,7 +323,7 @@ authentication: {
323323
}
324324
```
325325

326-
# [Kubernetes](#tab/kubernetes)
326+
# [Kubernetes (preview)](#tab/kubernetes)
327327

328328
```yaml
329329
authentication:
@@ -359,7 +359,7 @@ authentication: {
359359
}
360360
```
361361

362-
# [Kubernetes](#tab/kubernetes)
362+
# [Kubernetes (preview)](#tab/kubernetes)
363363

364364
```yaml
365365
authentication:
@@ -417,7 +417,7 @@ resource acrRegistryEndpoint 'Microsoft.IoTOperations/instances/registryEndpoint
417417
}
418418
```
419419

420-
# [Kubernetes](#tab/kubernetes)
420+
# [Kubernetes (preview)](#tab/kubernetes)
421421

422422
```yaml
423423
apiVersion: connectivity.iotoperations.azure.com/v1beta1

‎articles/iot-operations/connect-to-cloud/howto-configure-wasm-graph-definitions.md‎

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,22 @@
11
---
2-
title: Configure WebAssembly Graph Definitions For Data Flow Graphs (preview)
2+
title: Configure WebAssembly Graph Definitions For Data Flow Graphs
33
description: Learn how to create and configure WebAssembly graph definitions that define data processing workflows for Azure IoT Operations data flow graphs.
44
author: sethmanheim
55
ms.author: sethm
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: how-to
9-
ms.date: 12/10/2025
9+
ms.date: 12/17/2025
1010
ai-usage: ai-assisted
1111

1212
---
1313

14-
# Configure WebAssembly (WASM) graph definitions for data flow graphs (preview)
15-
16-
> [!IMPORTANT]
17-
> WebAssembly (WASM) graph definitions for data flow graphs are in PREVIEW. This feature has limitations and is not for production workloads.
18-
>
19-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or not yet released into general availability.
14+
# Configure WebAssembly (WASM) graph definitions for data flow graphs
2015

2116
Graph definitions are central to WASM development because they define how your modules connect to processing workflows. Understanding the relationship between graph definitions and data flow graphs helps you develop effectively.
2217

18+
WebAssembly (WASM) graph definitions for data flow graphs are generally available.
19+
2320
This article focuses on creating and configuring the YAML graph definitions. For information about deploying and testing WASM data flow graphs, see [Use WebAssembly with data flow graphs](howto-dataflow-graph-wasm.md).
2421

2522
> [!IMPORTANT]

‎articles/iot-operations/connect-to-cloud/howto-dataflow-graph-wasm.md‎

Lines changed: 15 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -6,20 +6,19 @@ ms.author: sethm
66
ms.service: azure-iot-operations
77
ms.subservice: azure-data-flows
88
ms.topic: how-to
9-
ms.date: 12/09/2025
9+
ms.date: 12/17/2025
1010
ai-usage: ai-assisted
1111

1212
---
1313

14-
# Use WebAssembly (WASM) with data flow graphs (preview)
14+
# Use WebAssembly (WASM) with data flow graphs
1515

16-
> [!IMPORTANT]
17-
> WebAssembly (WASM) with data flow graphs is in PREVIEW. This feature has limitations and isn't for production workloads.
18-
>
19-
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or not yet released into general availability.
16+
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
2017

2118
Azure IoT Operations data flow graphs support WebAssembly (WASM) modules for custom data processing at the edge. You can deploy custom business logic and data transformations as part of your data flow pipelines.
2219

20+
WebAssembly (WASM) with data flow graphs is generally available.
21+
2322
> [!TIP]
2423
> Want to run AI in-band? See [Run ONNX inference in WebAssembly data flow graphs](../develop-edge-apps/howto-wasm-onnx-inference.md) to package and execute small ONNX models inside your WASM operators.
2524
@@ -197,10 +196,7 @@ resource registryEndpoint 'Microsoft.IoTOperations/instances/registryEndpoints@2
197196
}
198197
```
199198

200-
# [Kubernetes](#tab/kubernetes)
201-
202-
> [!IMPORTANT]
203-
> This section includes instructions for managing Azure IoT Operations components using Kubernetes deployment manifests, which is in **preview**. This feature is provided with [several limitations](/azure/iot-operations/deploy-iot-ops/howto-manage-update-uninstall#preview-manage-components-using-kubernetes-deployment-manifests), and shouldn't be used for production workloads.
199+
# [Kubernetes (preview)](#tab/kubernetes)
204200

205201
```yaml
206202
apiVersion: connectivity.iotoperations.azure.com/v1
@@ -429,7 +425,7 @@ resource dataflowGraph 'Microsoft.IoTOperations/instances/dataflowProfiles/dataf
429425
}
430426
```
431427

432-
# [Kubernetes](#tab/kubernetes)
428+
# [Kubernetes (preview)](#tab/kubernetes)
433429

434430
Create a YAML file with the following configuration:
435431

@@ -710,7 +706,7 @@ resource complexDataflowGraph 'Microsoft.IoTOperations/instances/dataflowProfile
710706
}
711707
```
712708

713-
# [Kubernetes](#tab/kubernetes)
709+
# [Kubernetes (preview)](#tab/kubernetes)
714710

715711
```yaml
716712
apiVersion: connectivity.iotoperations.azure.com/v1
@@ -933,7 +929,7 @@ resource dataflowGraph 'Microsoft.IoTOperations/instances/dataflowProfiles/dataf
933929
}
934930
```
935931

936-
# [Kubernetes](#tab/kubernetes)
932+
# [Kubernetes (preview)](#tab/kubernetes)
937933

938934
```yaml
939935
apiVersion: connectivity.iotoperations.azure.com/v1
@@ -976,7 +972,7 @@ resource dataflowGraph 'Microsoft.IoTOperations/instances/dataflowProfiles/dataf
976972
}
977973
```
978974

979-
# [Kubernetes](#tab/kubernetes)
975+
# [Kubernetes (preview)](#tab/kubernetes)
980976

981977
```yaml
982978
apiVersion: connectivity.iotoperations.azure.com/v1
@@ -1023,7 +1019,7 @@ resource dataflowGraph 'Microsoft.IoTOperations/instances/dataflowProfiles/dataf
10231019
}
10241020
```
10251021

1026-
# [Kubernetes](#tab/kubernetes)
1022+
# [Kubernetes (preview)](#tab/kubernetes)
10271023

10281024
```yaml
10291025
apiVersion: connectivity.iotoperations.azure.com/v1
@@ -1076,7 +1072,7 @@ In the data flow diagram, select **Source** to configure the source node. Under
10761072
}
10771073
```
10781074

1079-
# [Kubernetes](#tab/kubernetes)
1075+
# [Kubernetes (preview)](#tab/kubernetes)
10801076

10811077
```yaml
10821078
- nodeType: Source
@@ -1136,7 +1132,7 @@ In the data flow diagram, select **Add graph transform (optional)** to add a gra
11361132
}
11371133
```
11381134

1139-
# [Kubernetes](#tab/kubernetes)
1135+
# [Kubernetes (preview)](#tab/kubernetes)
11401136

11411137
```yaml
11421138
- nodeType: Graph
@@ -1201,7 +1197,7 @@ For storage destinations like Azure Data Lake or Fabric OneLake, you can specify
12011197
}
12021198
```
12031199

1204-
# [Kubernetes](#tab/kubernetes)
1200+
# [Kubernetes (preview)](#tab/kubernetes)
12051201

12061202
```yaml
12071203
- nodeType: Destination
@@ -1253,7 +1249,7 @@ nodeConnections: [
12531249
]
12541250
```
12551251

1256-
# [Kubernetes](#tab/kubernetes)
1252+
# [Kubernetes (preview)](#tab/kubernetes)
12571253

12581254
```yaml
12591255
nodeConnections:

‎articles/iot-operations/manage-mqtt-broker/howto-configure-authorization.md‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -744,7 +744,8 @@ stateStoreResources: [
744744
]
745745
```
746746

747-
# [Kubernetes](#tab/kubernetes)
747+
# [Kubernetes (preview)](#tab/kubernetes)
748+
748749

749750
In your custom resource definition, include the `stateStoreResources` section in your authorization policy.
750751

@@ -1019,7 +1020,8 @@ Deploy the Bicep file by using the Azure CLI:
10191020
az deployment group create --resource-group <RESOURCE_GROUP> --template-file <FILE>.bicep
10201021
```
10211022

1022-
# [Kubernetes](#tab/kubernetes)
1023+
# [Kubernetes (preview)](#tab/kubernetes)
1024+
10231025

10241026
``` yaml
10251027
stateStoreResources:

0 commit comments

Comments
 (0)