Cluster Autoscaler should support multiple profiles

[daimaxiaxie]

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.:

The cluster scheduler can use multiple profiles to perform different scheduling for different pods. However, the current Cluster Autoscaler only supports one profile, which will lead to inaccurate scale up and down. So Cluster Autoscaler should support multiple profiles.

Describe the solution you'd like.:

Use the corresponding framework according to pod scheduler name in SchedulerBasedPredicateChecker.

Describe any alternative solutions you've considered.:

Added new predicate checker MultiSchedulerPredicateChecker, use flag enabled.

Additional context.:

NONE

[Shubham82]

/area cluster-autoscaler

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Shubham82]

/remove-lifecycle stale /lifecycle frozen