Skip to content

Commit f9dff5a

Browse files
committed
Formatting
1 parent 60e1eac commit f9dff5a

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/iot-operations/connect-to-cloud/howto-configure-kafka.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -211,7 +211,7 @@ To learn how to use Azure Key Vault and the `keyVault` to manage secrets for Azu
211211

212212
### Authenticate to Event Hubs
213213

214-
### [Managed identity](#tab/managed-identity)
214+
#### [Managed identity](#tab/managed-identity)
215215

216216
To use managed identity, specify it as the only method under authentication. You also need to assign a role to the managed identity that grants permission to send and receive messages from Event Hubs, such as Azure Event Hubs Data Owner or Azure Event Hubs Data Sender/Receiver. To learn more, see [Authenticate an application with Microsoft Entra ID to access Event Hubs resources](/azure/event-hubs/authenticate-application#built-in-roles-for-azure-event-hubs).
217217

@@ -249,7 +249,7 @@ spec:
249249
kubernetes: {}
250250
```
251251

252-
### [SASL](#tab/sasl)
252+
#### [SASL](#tab/sasl)
253253

254254
To connect to Event Hubs using a connection string and Kubernetes secret, use `plain` SASL type and `$ConnectionString` as the username and the full connection string as the password.
255255

@@ -296,7 +296,6 @@ spec:
296296
trustedCaCertificateConfigMap: "aio-ca-trust-bundle-test-only"
297297
authentication:
298298
kubernetes: {}
299-
300299
```
301300

302301
To use Azure Key Vault instead of Kubernetes secrets, create an Azure Key Vault secret with the connection string `Endpoint=sb://..`, reference it with `vaultSecret`, and specify the username as `"$ConnectionString"` in the configuration.
@@ -322,7 +321,7 @@ authentication:
322321
# version: 939ecc2...
323322
```
324323

325-
### [X.509](#tab/x509)
324+
#### [X.509](#tab/x509)
326325

327326
For X.509, use Kubernetes TLS secret containing the public certificate and private key.
328327

@@ -467,8 +466,8 @@ The compression field enables compression for the messages sent to Kafka topics.
467466
| ----- | ----------- | --------- |
468467
| none | No compression or batching is applied. *none* is the default value if no compression is specified. | Yes |
469468
| gzip | GZIP compression and batching are applied. GZIP is a general-purpose compression algorithm that offers a good balance between compression ratio and speed. [Event Hubs Premium](../../event-hubs/event-hubs-premium-overview.md) pricing tier is required for GZIP compression. | Yes |
470-
| Snappy | Snappy compression is not supported by [Azure Event Hubs](../../event-hubs/azure-event-hubs-kafka-overview.m#compression). | No. Use [Apache Kafka](https://kafka.apache.org) |
471-
| LZ4 | LZ4 compression is not supported by [Azure Event Hubs](../../event-hubs/azure-event-hubs-kafka-overview.md#compression). | No. Use [Apache Kafka](https://kafka.apache.org) |
469+
| snappy | Snappy compression is not supported by [Azure Event Hubs](../../event-hubs/azure-event-hubs-kafka-overview.m#compression). | No. Use [Apache Kafka](https://kafka.apache.org). |
470+
| lz4 | LZ4 compression is not supported by [Azure Event Hubs](../../event-hubs/azure-event-hubs-kafka-overview.md#compression). | No. Use [Apache Kafka](https://kafka.apache.org). |
472471

473472

474473
### Batching

0 commit comments

Comments
 (0)