Skip to content

[release/v1.8.x] Add provider manifest example for Azure Event Hub managed identity auth #1276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matheuscscp merged 1 commit into from
Mar 20, 2026
Merged

[release/v1.8.x] Add provider manifest example for Azure Event Hub managed identity auth #1276

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/spec/v1beta3/providers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1822,6 +1822,28 @@ for the client-id and tenant-id of the managed identity.
For a complete guide on how to set up authentication for an Azure Event Hub,
see the integration [docs](/flux/integrations/azure/).

##### Provider manifest

When using managed identity (workload identity), the provider uses the
`.spec.channel` and `.spec.address` fields to identify the Azure Event Hub:

- `channel` — the Azure Event Hub namespace
- `address` — the Azure Event Hub name

```yaml
---
apiVersion: notification.toolkit.fluxcd.io/v1beta3
kind: Provider
metadata:
name: azure
namespace: default
spec:
type: azureeventhub
address: <event-hub-name>
channel: <event-hub-namespace>
serviceAccountName: <sa-name> # if object-level workload identity is enabled.
```

#### SAS based auth

When using SAS auth, we only use the `address` field in the secret.
Expand Down
Loading