Trigger Specification
This specification describes the azure-eventhub trigger for Azure Event Hubs.
triggers:
- type: azure-eventhub
metadata:
connectionFromEnv: EVENTHUB_CONNECTIONSTRING_ENV_NAME
storageConnectionFromEnv: STORAGE_CONNECTIONSTRING_ENV_NAME
consumerGroup: $Default
unprocessedEventThreshold: '64'
activationUnprocessedEventThreshold: '10'
blobContainer: 'name_of_container'
# Optional (Default: AzurePublicCloud)
cloud: Private
# Required when cloud = Private
endpointSuffix: servicebus.airgap.example
# Required when cloud = Private.
activeDirectoryEndpoint: https://login.airgap.example/
# Required when cloud = Private.
eventHubResourceURL: https://eventhubs.airgap.example/
Parameter list:
connectionFromEnv- Name of the environment variable your deployment uses to get the connection string appended withEntityPath=<event_hub_name>.storageConnectionFromEnv- Name of the environment variable that provides connection string for Azure Storage Account to store checkpoint. As of now the Event Hub scaler only reads from Azure Blob Storage.consumerGroup- Consumer group of Azure Event Hub consumer. (default:$default, Optional)unprocessedEventThreshold- Average target value to trigger scaling actions. (Default:64, Optional)activationUnprocessedEventThreshold- Target value for activating the scaler. Learn more about activation here.(Default:0, Optional)blobContainer- Container name to store checkpoint. This is needed for everycheckpointStrategyexcept ofAzureFunction. With Azure Functions theblobContaineris autogenerated and cannot be overridden.checkpointStrategy- configure the checkpoint behaviour of different Event Hub SDKs. (Values:azureFunction,blobMetadata,goSdk, default:"", Optional)azureFunction- Suitable for Azure Functions & Azure WebJobs SDK. This is the default setting, whenblobcontaineris not specified.blobMetadata- For all implementations that store checkpoint information on blob metadata such as current C#, Python, Java and JavaScript Event Hub SDKs.goSdk- For all implementations using the Golang SDK’s checkpointing, for example Dapr.- When no checkpoint strategy is specified, the Event Hub scaler will use backwards compatibility and able to scale older implementations of C#, Python or Java Event Hub SDKs. (see “Legacy checkpointing”). If this behaviour should be used,
blobContaineris also required.
cloud- Name of the cloud environment that the Event Hub belongs to. (Values:AzurePublicCloud,AzureUSGovernmentCloud,AzureChinaCloud,AzureGermanCloud,Private, Default:AzurePublicCloud, Optional)endpointSuffix- Service Bus endpoint suffix of the cloud environment. (Required whencloudis set toPrivate, e.g.servicebus.cloudapi.deforAzureGermanCloud).activeDirectoryEndpoint- Active Directory endpoint of the cloud environment. (Required whencloudis set toPrivate, e.g.https://login.microsoftonline.de/forAzureGermanCloud).eventHubResourceURL- Event Hub resource URL of the cloud environment. (Required whencloudis set toPrivate, e.g.https://eventhubs.azure.net/for known Azure Clouds).
💡 Learn more about the checkpointing behaviour in this section.
💡 The Azure Storage connection string is not compatible with connection string created from a Shared Access Signature.
Authentication Parameters
You can authenticate by using pod identity or connection string authentication.
Connection String Authentication:
-
connection- Connection string for the Azure Event Hubs Namespace.The following formats are supported.
- With SharedAccessKey -
Endpoint=sb://<sb>.servicebus.windows.net/;SharedAccessKeyName=<key name>;SharedAccessKey=<key value>;EntityPath=<hub-name>.
- With SharedAccessKey -
-
storageConnection- Connection string for the Azure Storage Account used to store checkpoint information.
💡 When providing
connection,EntityPathis optional. If it is not provided, theneventHubNamemust be used to provide the name of the Azure Event Hub instance to use inside the namespace.
Pod identity based authentication:
Azure AD Pod Identity or Azure AD Workload Identity providers can be used.
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
name: nameOfTriggerAuth
namespace: default
spec:
podIdentity:
provider: Azure | azure-workload
When you do so, the Event Hub scaler will depend on the existence of two configurations you have to provide: eventHubNamespace and eventHubName.
Checkpointing Behaviour
The list of available checkpointing strategies can be found in the trigger specification section. The way checkpoints are stored has changed with updates to the EventHub SDKs.
-
Legacy behaviour: The older implementations are based on the
EventProcessorHostclient, which stores the checkpoint information as contents of the storage blob. This is the default behaviour when nocheckpointStrategyis specified. This is applicable for the following scenarios:- .NET applications using
Microsoft.Azure.EventHubsNuGet package. - Java applications using
azure-eventhubs-ephpackage. - Python applications using
azure-eventhubpackage below v5.
- .NET applications using
-
Current behaviour: The newer implementations are based on the
EventProcessorClient, which stores the checkpoint information as metadata on the storage blob. This is the behaviour whencheckpointStrategyis set toblobMetadata. This is applicable for the following scenarios:- .NET applications using
Azure.Messaging.EventHubsNuGet package. - Python applications using
azure-eventhubv5. - .NET Azure Functions using
Microsoft.Azure.WebJobs.Extensions.EventHubsv5. - Azure Functions in other languages using
Microsoft.Azure.Functions.ExtensionBundlev3.
- .NET applications using
💡
blobContainername is required for applications following legacy behaviour.
💡 Users should set
blobContainertoazure-webjobs-eventhubfor Azure Functions usingblobMetadataascheckpointStrategy.
Example
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: azure-eventhub-scaledobject
namespace: default
spec:
scaleTargetRef:
name: azureeventhub-function
triggers:
- type: azure-eventhub
metadata:
# Required
storageConnectionFromEnv: AzureWebJobsStorage
# Required if not using Pod Identity
connectionFromEnv: EventHub
# Required if using Pod Identity
eventHubNamespace: AzureEventHubNameSpace
eventHubName: NameOfTheEventHub
# Optional
consumerGroup: $Default # default: $Default
unprocessedEventThreshold: '64' # default 64 events.
blobContainer: ehcontainer