-
Notifications
You must be signed in to change notification settings - Fork 726
Is there a plan on "Integration with metrics providers for obtaining real load metrics" #123
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
Comments
Yes, so to have this feature in descheduler, first it would require that default scheduler also supports scheduling based on actual usage of resources. |
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. |
…tream WRKLDS-1586: Sync with upstream
I found this feature from the roadmap and I thought it involves real-time scheduling which is quite different from the current logic.
The text was updated successfully, but these errors were encountered: