Skip to content

Commit 467862f

Browse files
authored
Merge pull request #1275 from dipti-pai/azeventhub-doc-update
Add provider manifest example for Azure Event Hub managed identity auth
2 parents 27e6dcc + 221b836 commit 467862f

1 file changed

Lines changed: 22 additions & 0 deletions

File tree

docs/spec/v1beta3/providers.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1822,6 +1822,28 @@ for the client-id and tenant-id of the managed identity.
18221822
For a complete guide on how to set up authentication for an Azure Event Hub,
18231823
see the integration [docs](/flux/integrations/azure/).
18241824

1825+
##### Provider manifest
1826+
1827+
When using managed identity (workload identity), the provider uses the
1828+
`.spec.channel` and `.spec.address` fields to identify the Azure Event Hub:
1829+
1830+
- `channel` — the Azure Event Hub namespace
1831+
- `address` — the Azure Event Hub name
1832+
1833+
```yaml
1834+
---
1835+
apiVersion: notification.toolkit.fluxcd.io/v1beta3
1836+
kind: Provider
1837+
metadata:
1838+
name: azure
1839+
namespace: default
1840+
spec:
1841+
type: azureeventhub
1842+
address: <event-hub-name>
1843+
channel: <event-hub-namespace>
1844+
serviceAccountName: <sa-name> # if object-level workload identity is enabled.
1845+
```
1846+
18251847
#### SAS based auth
18261848

18271849
When using SAS auth, we only use the `address` field in the secret.

0 commit comments

Comments
 (0)