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

kpack operator triggered rebuilds lead to cluster starvation #774

Closed
sambhav opened this issue Jul 19, 2021 · 0 comments · Fixed by #908
Closed

kpack operator triggered rebuilds lead to cluster starvation #774

sambhav opened this issue Jul 19, 2021 · 0 comments · Fixed by #908
Labels
good first issue Good for newcomers

Comments

@sambhav
Copy link
Contributor

sambhav commented Jul 19, 2021

If the operator triggers a rebuild across the cluster due to a change in a buildpack, kpack currently schedules a lot of builds which may cause user submitted image/builds to be queued/starved for a long time. We should ideally implement rate-limiting or priority queues for rebuilds triggered automatically v/s by a user.
@sambhav sambhav changed the title kpack operator trigger rebuilds lead to cluster starvation kpack operator triggered rebuilds lead to cluster starvation Aug 11, 2021
@matthewmcnew matthewmcnew added the good first issue Good for newcomers label Oct 20, 2021
@sambhav sambhav mentioned this issue Dec 24, 2021
Merged
@mvalliath mvalliath mentioned this issue Feb 3, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add priority classes to builds based on change reason sambhav/kpack
2 participants
@matthewmcnew @sambhav