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.

Target burst capacity can be configured using a combination of the following parameters:

• Setting the targeted concurrency limits for the revision. See concurrency.
• Setting the target utilization parameters. See .

• Global key: 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)

Per Revision

Global (ConfigMap)

• If autoscaling.knative.dev/targetBurstCapacity is set to , the Activator is only added to the request path during scale from zero scenarios, and ingress load balancing will be applied.

Note

Ingress gateway load balancing requires additional configuration. For more information about load balancing using an ingress gateway, see the Serving API 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.