In a typical deployment, a service keeps running even when it's completely idle and waiting for incoming requests or messages. Resources are reserved to handle any possible higher load.
When using a scale-to-zero strategy, an idle service has all its instances stopped. Any inbound traffic triggers an activation of the service. Something needs to track the triggers that will activate the service and manage the inbound traffic while the service is scaled back up from zero.
[
add
]
[
|
|
...
]