Closed qianlei90 closed 2 weeks ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Which component are you using?:
cluster-autoscaler
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
We imported the scheduler framework and utilized the PreFilter and Filter for schedule simulation. However, cluster autoscale does not currently support schedule plugins in https://github.com/kubernetes-sigs/scheduler-plugins.
I understand that there is currently no way to support these plugins. What issues will we encounter if we introduce schedule config and schedule plugins?
Describe the solution you'd like.:
Can we create a remote dry-run scheduler that runs a gRPC server to receive ClusterSnapshot, pending pods, and predict the target nodes? This will allow us to move the scheduling logic out of cluster-autoscaler and enable support for custom scheduling plugins in the remote scheduler.
Describe any alternative solutions you've considered.:
Additional context.: