Epic Goal

• Add the Cluster Autoscaler ProvisioingRequest CRD to OpenShift

Why is this important?

• The ProvisioningRequest CRD provides users with a mechanism to inform the cluster autoscaler about upcoming workloads and the resources they will need so that any new compute resources can begin provisioning before the workload lands. Day 2 tools such as Kueue also have integration with the ProvisioingRequest to support this predictive scaling behavior. The ProvisioingRequest feature gives users new ability to improve the performance of their clusters by reducing the time to add new nodes for upcoming workloads.

Scenarios

1. As a Kueue user, having ProvisioingRequest support allows me to reduce the time necessary for new nodes to be added to my cluster for workloads coming from Kueue. This reduction in time gives better performance by decreasing the amount of time spent waiting for new cluster resources to be added for pending workloads.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. None

Previous Work:

1. https://github.com/openshift/kubernetes-autoscaler/blob/master/cluster-autoscaler/proposals/provisioning-request.md

Open questions::

1. Do we need to collaborate with the console team to make the usage and monitoring of ProvisioningRequests more user friendly?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Downstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>