-
Notifications
You must be signed in to change notification settings - Fork 132
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
Need to abstract GetClusterStatus to be part of the controller plugin #10
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
fix: add missing cluster role rules Signed-off-by: ajayk <ajaykemparaj@gmail.com>
fix: add missing cluster role rules
The ultimate goal of this autoscaler is to support any types of cluster statuses for controllers. In current implementation, only cluster size(node number and core number) is consider as part of the cluster size. Soon it will become not sufficient because cluster size is not always an appropriate parameters for scaling applications.
Another obvious option for scaling is pods number with QPS per pod. Or even metrics retrieved from some other applications in the same cluster. To support any possible type for cluster status, I think abstracting GetClusterStatus() also into controller would be a good choice.
The text was updated successfully, but these errors were encountered: