Custom Scalers in Azure Container Apps¶

Custom scalers let you bring KEDA-backed trigger types into Azure Container Apps when HTTP, CPU, memory, or the common event examples are not enough. The Container Apps platform documents this as custom scaling based on ScaledObject scalers.

Custom rule shape¶

template:
  scale:
    minReplicas: 0
    maxReplicas: 20
    rules:
      - name: custom-rule
        custom:
          type: <scaler-type>
          metadata:
            <key>: <value>
          auth:
            - secretRef: <secret-name>
              triggerParameter: <parameter-name>

flowchart TD
    A[Choose workload signal] --> B{Built-in rule enough?}
    B -->|Yes| C[Use HTTP or resource rule]
    B -->|No| D[Use custom KEDA scaler type]
    D --> E[Provide metadata and auth]
    E --> F[Test scaler behavior before production]

What Microsoft Learn confirms¶

• Container Apps supports custom scale rules.
• These rules are based on KEDA ScaledObject scalers.
• Authentication can be wired with secret mappings or managed identity.

Authentication patterns¶

Use these patterns when the scaler needs credentials:

• secretRef for trigger parameters that expect a named secret
• identity when the scaler supports managed identity

Example: generic custom scaler shape¶

{
  "name": "custom-trigger",
  "custom": {
    "type": "<scaler-type>",
    "metadata": {
      "<key>": "<value>"
    },
    "auth": [
      {
        "secretRef": "<secret-name>",
        "triggerParameter": "<parameter-name>"
      }
    ]
  }
}

Example: cron or Prometheus-style bring-your-own scaler¶

A safe operating pattern is:

1. define the custom scaler type and metadata in infrastructure code
2. wire secrets or identity explicitly
3. validate scaling in a non-production environment
4. keep maxReplicas conservative until observed behavior is understood

See Also¶

• Scaling Overview
• Event Scalers
• Scaling Rules Reference
• Scaling Best Practices

Sources¶

• Set scaling rules in Azure Container Apps (Microsoft Learn)