1. Proposed title of this feature request

Enabling Cluster Autoscaling with CAPM3/CAPOA

2. What is the nature and description of the request?

There is currently no support for autoscaling with Metal3.  Customers that use Metal3 would be able to leverage capabilities of autoscaling in bare-metal, on-prem environments similar to autoscaling in cloud environments.

3. Why does the customer need this? (List the business requirements here)

For more efficient use of on-prem hardware infrastructure.
They are talking at least 3 different levels this could be taken to: * easy: shut down/power on worker nodes when cluster has spare capacity over/under X threshold (saves power/cooling)

• medium: add-in/remove extra/pre-configured compute HW capacity as needed (this will allow for spare hw to be re-purposed manually)
• hard: fully automated re-allocation of compute HW capacity between clusters allowing compute HW to float between (this requires a fully automated and managed core infrastructure beyond just OpenShift - i.e.: dynamic networking, dynamic storage, etc.)

4. List any affected packages or components.

CAS, Cluster API