Trigger Specification

This specification describes the azure-blob trigger for Azure Blob Storage. It scales based on the count of blobs in a given blob storage container and assumes the worker is responsible for clearing the container by delete/move the blobs once the blob processing completed.

triggers:
- type: azure-blob
  metadata:
    blobContainerName: functions-blob
    blobCount: '5'
    connectionFromEnv: STORAGE_CONNECTIONSTRING_ENV_NAME
    blobPrefix: myprefix
    blobDelimiter: /example

Parameter list:

• blobContainerName - Name of container in an Azure Storage account
• blobCount - Average target value to trigger scaling actions. (default: 5)
• connectionFromEnv - Name of the environment variable your deployment uses to get the connection string.
• blobPrefix - Prefix for the Blob. Use this to specifiy sub path for the blobs if required. (default: "")
• blobDelimiter - Delimiter for identifying the blob prefix. (default: /)

Authentication Parameters

You can authenticate by using pod identity or connection string authentication.

Connection String Authentication:

• connection - Connection string for Azure Storage Account

Example

apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
  name: azure-blob-auth
spec:
  podIdentity:
    provider: azure
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: azure-blob-scaledobject
  namespace: default
spec:
  scaleTargetRef:
    name: azureblob-function
  triggers:
  - type: azure-blob
    metadata:
      # Required
      blobContainerName: functionsblob
      # Optional
      blobCount: "5" # default 5
      blobPrefix: blobsubpath # Default : ""
      blobDelimiter: "/" # Default: "/"
    authenticationRef:
        name: azure-blob-auth # authenticationRef would need either podIdentity or define a connection parameter

Currently available scalers for KEDA