Skip to content

[WIP] Define autoscaling for Knative Eventing #2901

Closed
@aslom

Description

Problem
Users of Knative Eventing expect that autoscaling is available and works. We should define what autoscaling for Knative Eventing means and how user experience would work to make it serverless and Knative-way.

Persona:
All personas

Exit Criteria
Documented what autoscaling should be in Knative Eventing

Time Estimate (optional):
2w

Additional context (optional)
This is outcome of discussion about building autoscaling annotations where we realized that before we define technical mechanisms (such as using annotations) we need first to define what we mean by "autoscaling" in Knative Eventing

Metadata

Assignees

No one assigned

    Labels

    area/performancekind/feature-requestlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions