Skip to content

Commit b2647b9

Browse files
author
Jill Grant
authored
Merge pull request #290229 from jlian/release-aio-ga
Managing via Kubernetes is in preview
2 parents 7e7b7be + d08407b commit b2647b9

22 files changed

+245
-172
lines changed

‎articles/iot-operations/connect-to-cloud/concept-dataflow-conversions.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ ms.service: azure-iot-operations
1313

1414
# Convert data by using dataflow conversions
1515

16+
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
17+
1618
You can use dataflow conversions to transform data in Azure IoT Operations. The *conversion* element in a dataflow is used to compute values for output fields. You can use input fields, available operations, data types, and type conversions in dataflow conversions.
1719

1820
The dataflow conversion element is used to compute values for output fields:
@@ -28,7 +30,7 @@ output: 'ColorProperties.*'
2830
expression: '($1 + $2) / 2'
2931
```
3032

31-
# [Kubernetes](#tab/kubernetes)
33+
# [Kubernetes (preview)](#tab/kubernetes)
3234

3335
```yaml
3436
- inputs:
@@ -64,7 +66,7 @@ output: 'ColorProperties.*'
6466
expression: '($1, $2, $3, $4)'
6567
```
6668
67-
# [Kubernetes](#tab/kubernetes)
69+
# [Kubernetes (preview)](#tab/kubernetes)
6870
6971
```yaml
7072
- inputs:
@@ -171,7 +173,7 @@ output: 'Measurement'
171173
expression: 'min($1)'
172174
```
173175

174-
# [Kubernetes](#tab/kubernetes)
176+
# [Kubernetes (preview)](#tab/kubernetes)
175177

176178
```yaml
177179
- inputs:
@@ -196,7 +198,7 @@ output: 'Measurements'
196198
expression: 'take($1, 10)' // taking at max 10 items
197199
```
198200

199-
# [Kubernetes](#tab/kubernetes)
201+
# [Kubernetes (preview)](#tab/kubernetes)
200202

201203
```yaml
202204
- inputs:
@@ -222,7 +224,7 @@ output: 'stats'
222224
expression: '($1, $2, $3, $4)'
223225
```
224226

225-
# [Kubernetes](#tab/kubernetes)
227+
# [Kubernetes (preview)](#tab/kubernetes)
226228

227229
```yaml
228230
- inputs:
@@ -280,7 +282,7 @@ output: 'BaseSalary'
280282
expression: 'if($1 == (), $2, $1)'
281283
```
282284

283-
# [Kubernetes](#tab/kubernetes)
285+
# [Kubernetes (preview)](#tab/kubernetes)
284286

285287
```yaml
286288
- inputs:

‎articles/iot-operations/connect-to-cloud/concept-dataflow-enrich.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ ms.service: azure-iot-operations
1313

1414
# Enrich data by using dataflows
1515

16+
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
17+
1618
You can enrich data by using the *contextualization datasets* function. When incoming records are processed, you can query these datasets based on conditions that relate to the fields of the incoming record. This capability allows for dynamic interactions. Data from these datasets can be used to supplement information in the output fields and participate in complex calculations during the mapping process.
1719

1820
For example, consider the following dataset with a few records, represented as JSON records:
@@ -47,7 +49,7 @@ datasets: [
4749
]
4850
```
4951

50-
# [Kubernetes](#tab/kubernetes)
52+
# [Kubernetes (preview)](#tab/kubernetes)
5153

5254
```yaml
5355
datasets:
@@ -84,7 +86,7 @@ When a new record is being processed, the mapper performs the following steps:
8486
}
8587
```
8688

87-
# [Kubernetes](#tab/kubernetes)
89+
# [Kubernetes (preview)](#tab/kubernetes)
8890

8991
```yaml
9092
- inputs:
@@ -127,7 +129,7 @@ datasets: [
127129
]
128130
```
129131

130-
# [Kubernetes](#tab/kubernetes)
132+
# [Kubernetes (preview)](#tab/kubernetes)
131133

132134
```yaml
133135
datasets:
@@ -157,7 +159,7 @@ inputs: [
157159
]
158160
```
159161

160-
# [Kubernetes](#tab/kubernetes)
162+
# [Kubernetes (preview)](#tab/kubernetes)
161163

162164
```yaml
163165
- inputs:
@@ -184,7 +186,7 @@ datasets: [
184186
]
185187
```
186188

187-
# [Kubernetes](#tab/kubernetes)
189+
# [Kubernetes (preview)](#tab/kubernetes)
188190

189191
```yaml
190192
datasets:

‎articles/iot-operations/connect-to-cloud/concept-dataflow-mapping.md

Lines changed: 24 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ ms.service: azure-iot-operations
1414

1515
# Map data by using dataflows
1616

17+
[!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
18+
1719
Use the dataflow mapping language to transform data in Azure IoT Operations. The syntax is a simple, yet powerful, way to define mappings that transform data from one format to another. This article provides an overview of the dataflow mapping language and key concepts.
1820

1921
Mapping allows you to transform data from one format to another. Consider the following input record:
@@ -86,7 +88,7 @@ The following mapping is an example:
8688
}
8789
```
8890

89-
# [Kubernetes](#tab/kubernetes)
91+
# [Kubernetes (preview)](#tab/kubernetes)
9092

9193
```yaml
9294
- inputs:
@@ -131,7 +133,7 @@ inputs: [
131133
output: 'origin_topic'
132134
```
133135

134-
# [Kubernetes](#tab/kubernetes)
136+
# [Kubernetes (preview)](#tab/kubernetes)
135137

136138
```yaml
137139
inputs:
@@ -152,7 +154,7 @@ inputs: [
152154
output: '$metadata.user_property.origin_topic'
153155
```
154156

155-
# [Kubernetes](#tab/kubernetes)
157+
# [Kubernetes (preview)](#tab/kubernetes)
156158

157159
```yaml
158160
inputs:
@@ -182,7 +184,7 @@ inputs: [
182184
]
183185
```
184186

185-
# [Kubernetes](#tab/kubernetes)
187+
# [Kubernetes (preview)](#tab/kubernetes)
186188

187189
```yaml
188190
- inputs:
@@ -201,7 +203,7 @@ inputs: [
201203
]
202204
```
203205

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

206208
```yaml
207209
- inputs:
@@ -220,7 +222,7 @@ inputs: [
220222
]
221223
```
222224

223-
# [Kubernetes](#tab/kubernetes)
225+
# [Kubernetes (preview)](#tab/kubernetes)
224226

225227
```yaml
226228
- inputs:
@@ -242,7 +244,7 @@ Any other characters are treated as part of the field name. This flexibility is
242244

243245
In Bicep, all strings are enclosed in single quotation marks (`'`). The examples about proper quoting in YAML for Kubernetes use don't apply.
244246

245-
# [Kubernetes](#tab/kubernetes)
247+
# [Kubernetes (preview)](#tab/kubernetes)
246248

247249
The path definition must also adhere to the rules of YAML. When a character with special meaning is included in the path, proper quoting is required in the configuration. Consult the YAML documentation for precise rules. Here are some examples that demonstrate the need for careful formatting:
248250

@@ -266,7 +268,7 @@ inputs: [
266268
]
267269
```
268270

269-
# [Kubernetes](#tab/kubernetes)
271+
# [Kubernetes (preview)](#tab/kubernetes)
270272

271273
```yaml
272274
- inputs:
@@ -291,7 +293,7 @@ In this example, the path consists of three segments: `Payload`, `Tag.10`, and `
291293
]
292294
```
293295

294-
# [Kubernetes](#tab/kubernetes)
296+
# [Kubernetes (preview)](#tab/kubernetes)
295297

296298
```yaml
297299
- inputs:
@@ -310,7 +312,7 @@ In this example, the path consists of three segments: `Payload`, `Tag.10`, and `
310312
]
311313
```
312314

313-
# [Kubernetes](#tab/kubernetes)
315+
# [Kubernetes (preview)](#tab/kubernetes)
314316

315317
```yaml
316318
- inputs:
@@ -329,7 +331,7 @@ In this example, the path consists of three segments: `Payload`, `Tag.10`, and `
329331
]
330332
```
331333

332-
# [Kubernetes](#tab/kubernetes)
334+
# [Kubernetes (preview)](#tab/kubernetes)
333335

334336
```yaml
335337
- inputs:
@@ -360,7 +362,7 @@ inputs: [
360362
output: '*'
361363
```
362364
363-
# [Kubernetes](#tab/kubernetes)
365+
# [Kubernetes (preview)](#tab/kubernetes)
364366
365367
```yaml
366368
- inputs:
@@ -419,7 +421,7 @@ Mapping configuration that uses wildcards:
419421
}
420422
```
421423

422-
# [Kubernetes](#tab/kubernetes)
424+
# [Kubernetes (preview)](#tab/kubernetes)
423425

424426
```yaml
425427
- inputs:
@@ -494,7 +496,7 @@ output: 'ColorProperties.*'
494496
expression: '($1 + $2) / 2'
495497
```
496498

497-
# [Kubernetes](#tab/kubernetes)
499+
# [Kubernetes (preview)](#tab/kubernetes)
498500

499501
```yaml
500502
- inputs:
@@ -566,7 +568,7 @@ inputs: [
566568
]
567569
```
568570

569-
# [Kubernetes](#tab/kubernetes)
571+
# [Kubernetes (preview)](#tab/kubernetes)
570572

571573
```yaml
572574
- inputs:
@@ -604,7 +606,7 @@ inputs: [
604606
]
605607
```
606608

607-
# [Kubernetes](#tab/kubernetes)
609+
# [Kubernetes (preview)](#tab/kubernetes)
608610

609611
```yaml
610612
- inputs:
@@ -645,7 +647,7 @@ When you use the previous example from multi-input wildcards, consider the follo
645647
}
646648
```
647649

648-
# [Kubernetes](#tab/kubernetes)
650+
# [Kubernetes (preview)](#tab/kubernetes)
649651

650652
```yaml
651653
- inputs:
@@ -709,7 +711,7 @@ Now, consider a scenario where a specific field needs a different calculation:
709711
}
710712
```
711713

712-
# [Kubernetes](#tab/kubernetes)
714+
# [Kubernetes (preview)](#tab/kubernetes)
713715

714716
```yaml
715717
- inputs:
@@ -753,7 +755,7 @@ Consider a special case for the same fields to help decide the right action:
753755
}
754756
```
755757

756-
# [Kubernetes](#tab/kubernetes)
758+
# [Kubernetes (preview)](#tab/kubernetes)
757759

758760
```yaml
759761
- inputs:
@@ -805,7 +807,7 @@ inputs: [
805807
output: 'Employment.BaseSalary'
806808
```
807809

808-
# [Kubernetes](#tab/kubernetes)
810+
# [Kubernetes (preview)](#tab/kubernetes)
809811

810812
```yaml
811813
- inputs:
@@ -826,7 +828,7 @@ inputs: [
826828
output: 'Employment.*'
827829
```
828830

829-
# [Kubernetes](#tab/kubernetes)
831+
# [Kubernetes (preview)](#tab/kubernetes)
830832

831833
```yaml
832834
- inputs:
@@ -863,7 +865,7 @@ inputs: [
863865
output: 'Thermostat.Temperature'
864866
```
865867

866-
# [Kubernetes](#tab/kubernetes)
868+
# [Kubernetes (preview)](#tab/kubernetes)
867869

868870
```yaml
869871
- inputs:

0 commit comments

Comments
 (0)