From cace0eb6c8464d63cc4c640f2c617054961a46dd Mon Sep 17 00:00:00 2001 From: Dipti Pai Date: Thu, 19 Mar 2026 08:58:53 -0700 Subject: [PATCH] Add provider manifest example for Azure Event Hub managed identity auth Document the channel and address field mapping when using workload identity with Azure Event Hub: - channel maps to the Event Hub namespace - address maps to the Event Hub name Signed-off-by: Dipti Pai (cherry picked from commit 221b8365a3a12f320164dbb97f377f0febf4a70e) --- docs/spec/v1beta3/providers.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/spec/v1beta3/providers.md b/docs/spec/v1beta3/providers.md index 3577b6d24..fc2a1988b 100644 --- a/docs/spec/v1beta3/providers.md +++ b/docs/spec/v1beta3/providers.md @@ -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: + channel: + serviceAccountName: # if object-level workload identity is enabled. +``` + #### SAS based auth When using SAS auth, we only use the `address` field in the secret.