Epic Goal

• Research Karpenter and Cluster API code to develop a detailed plan for creating a Cluster API provider to Karpenter.

Why is this important?

• Integrating Karpenter with OpenShift will need to pay special attention to OpenShift's machine management layer. This layer is currently handled by the Machine API but in the future will migrate to use Cluster API. Creating a Cluster API provider for Karpenter has the potential to unlock all of the supported Cluster API platforms.

Scenarios

1. As an OpenShift administrator, I would like to run Karpenter on any provider so that I can utilize features such as pod consolidation, which does not exist in the Kubernetes Cluster Autoscaler, so that i can have more efficient resource usage in our clusters.

Acceptance Criteria

• Document created with detailed plan for Karpenter integration with Cluster API on OpenShift
• Enhancement proposed to upstream Cluster API community with integration plans.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation 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>