Skip to content

Commit 438b3c4

Browse files
Added some spacing
1 parent 5019bfa commit 438b3c4

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

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

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -251,7 +251,9 @@ spec:
251251

252252
### [SASL](#tab/sasl)
253253

254-
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. First create the Kubernetes secret:
254+
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.
255+
256+
First create the Kubernetes secret:
255257

256258
```bash
257259
kubectl create secret generic cs-secret -n azure-iot-operations \
@@ -297,7 +299,9 @@ spec:
297299
298300
```
299301

300-
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. Use the previous YAML example and change the authentication section to the following:
302+
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.
303+
304+
Use the previous YAML example and change the authentication section to the following:
301305

302306
```yaml
303307
authentication:
@@ -363,7 +367,9 @@ spec:
363367
kubernetes: {}
364368
```
365369

366-
To use Azure Key Vault instead, make sure the [certificate and private key are properly imported](../../key-vault/certificates/tutorial-import-certificate.md) and then specify the reference with `vaultCert`. Use the previous YAML example and change the authentication section to the following:
370+
To use Azure Key Vault instead, make sure the [certificate and private key are properly imported](../../key-vault/certificates/tutorial-import-certificate.md) and then specify the reference with `vaultCert`.
371+
372+
Use the previous YAML example and change the authentication section to the following:
367373

368374
```yaml
369375
authentication:

0 commit comments

Comments
 (0)