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.

Sign up for GitHub

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

Jump to bottom

Improve scaling in Knative Eventing #4494

Closed
aslom opened this issue Nov 10, 2020 · 4 comments
Closed

Improve scaling in Knative Eventing #4494

aslom opened this issue Nov 10, 2020 · 4 comments
Labels
area/observability 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
Backlog

Comments

@aslom
Copy link
Member

aslom commented Nov 10, 2020

Problem
This is umbrella issue to gather pointers to various efforts to improve scaling in Knative Eventing

Persona:
Which persona is this feature for?
System Integrator
Contributors

Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Links to related feature docs, issues, PRs, testing results, etc.

Time Estimate (optional):
How many developer-days do you think this may take to resolve?
months

Additional context (optional)
Add any other context about the feature request here.
Prompted by @lberk comment #4462 (comment)
@aslom
Copy link
Member Author

aslom commented Nov 10, 2020 •
edited
Loading

Following work on autoscaling and feature proposal doc I have opened issue and started implementing simple tests for scaling: #4462

@aslom
Copy link
Member Author

aslom commented Nov 10, 2020 •
edited
Loading

Related issue: Make pull-based receive adapter HA and scalable #3157

@aslom
Copy link
Member Author

aslom commented Nov 10, 2020 •
edited
Loading

There was also very good discussions few moths ago in two issues:

@grantr grantr added area/performance area/observability priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Nov 16, 2020
@grantr grantr added this to the Backlog milestone Nov 16, 2020
@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 Feb 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/observability 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
Milestone
Backlog
Development

No branches or pull requests
2 participants
@grantr @aslom