Skip to content

Kafka functions: KEDA scaling with consumer-lag trigger #3934

Description

@aliok

func deploy already supports --deployer keda for KEDA-based scaling. For Kafka functions, add a Kafka consumer-lag trigger so KEDA can scale based on consumer group lag — enabling scale-to-zero when there are no messages and scaling up under load. Currently Kafka functions require min-scale: 1 to stay running.

Traffic-based autoscaling (e.g. Knative's KPA or KEDA HTTP scaler) does not work for Kafka functions because there is no inbound HTTP traffic — the function pulls messages from Kafka internally. Scaling must be driven by Kafka consumer group lag instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions