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

Autoscaling based on processors #5823

Closed
barkbay opened this issue Jun 23, 2022 · 0 comments · Fixed by #5924
Closed

Autoscaling based on processors #5823

barkbay opened this issue Jun 23, 2022 · 0 comments · Fixed by #5924
Assignees
@barkbay
Labels
autoscaling discuss We need to figure this out >enhancement Enhancement of existing functionality

Comments

@barkbay
Copy link
Contributor

barkbay commented Jun 23, 2022

Some deciders should soon include a processors field in the autoscaling capacity response: elastic/elasticsearch#87895

We should evaluate how this information can be used by the operator.
@botelastic botelastic bot added the triage label Jun 23, 2022
@barkbay barkbay added >enhancement Enhancement of existing functionality discuss We need to figure this out and removed triage labels Jun 23, 2022
@barkbay barkbay self-assigned this Aug 3, 2022
@barkbay barkbay mentioned this issue Aug 3, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@barkbay barkbay

Labels
autoscaling discuss We need to figure this out >enhancement Enhancement of existing functionality
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Autoscaling] Add CPU recommender barkbay/cloud-on-k8s
1 participant
@barkbay