Configuring target burst capacity

    The Activator service is responsible for receiving and buffering requests for inactive revisions, or for revisions where a traffic burst is larger than the limits of what can be handled without buffering for that revision. It can also quickly spin up additional pods for capacity, and throttle how quickly requests are sent to pods.

    • Setting the targeted concurrency limits for the revision. See concurrency.
    • Setting the target utilization parameters. See .
    • Setting the target burst capacity. You can configure target burst capacity using the annotation key in the config-autoscaler ConfigMap. See Setting the target burst capacity.
    • Per-revision annotation key: autoscaling.knative.dev/targetBurstCapacity
    • Possible values: float ( means the Activator is only in path when scaled to 0, -1 means the Activator is always in path)
    • Default: 200

    Example:

    • NOTE: Ingress gateway load balancing requires additional configuration. For more information about load balancing using an ingress gateway, see the documentation.

    • If autoscaling.knative.dev/targetBurstCapacity is set to another integer, the Activator may be in the path, depending on the revision scale and load.