Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Define autoscaling for Knative Eventing #2901

Closed
aslom opened this issue Apr 2, 2020 · 10 comments
Closed

[WIP] Define autoscaling for Knative Eventing #2901

aslom opened this issue Apr 2, 2020 · 10 comments
Labels
area/performance kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@aslom
Copy link
Member

aslom commented Apr 2, 2020

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

@aslom
Copy link
Member Author

aslom commented Apr 2, 2020

Please view, comment and edit proposals for autoscaling goals in public google doc:
https://docs.google.com/document/d/1usNmsuHBWzVaL5GGC873iGVrkKXGbc6t7bLHJL38Cyg/edit?usp=sharing

/cc @grantr @vaikas @matzew @lionelvillard

@grantr
Copy link
Contributor

grantr commented Apr 6, 2020

@aslom is there a single tracking issue that we can link all the autoscaling bugs to? That will make these easier to triage. Thanks!

@grantr grantr added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 6, 2020
@lberk
Copy link
Member

lberk commented Apr 6, 2020

Hi, what is the overlap (and can we get a single tracker for) all these related issues?
#2161
#2154
#2153
#2152

@aslom
Copy link
Member Author

aslom commented Apr 6, 2020

@lberk they all talk about "scaling" different part of KnE - I hope we can reach here consensus on definition of (auto)scaling in Knative Eventing and then apply it to plan what we do those parts

@grantr
Copy link
Contributor

grantr commented Apr 6, 2020

Sounds like you'd like this issue to be the overall tracking issue then?

@aslom
Copy link
Member Author

aslom commented Jul 21, 2020

Putting together google doc to summarize options: https://docs.google.com/document/d/18Ma-uqsB0SYzwvRZ_rz5c8m21JAXGP0oLZpr8W0Jwak/edit?usp=sharing

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 25, 2020
@aslom
Copy link
Member Author

aslom commented Dec 6, 2020

/reopen

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 23, 2021
@slinkydeveloper
Copy link
Contributor

Is this still relevant? Since I see you worked on this in more specific issues, can we close this more general issue?

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance kind/feature-request lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

4 participants