Feature Overview (aka. Goal Summary)  

This is a upstream work and not impacting the release of OpenShift 4.17.
This feature covers the work done upstream to create a CAPI provider for Karpenter. Feature will also document the unsupported way  to integrate Karpenter with HCP on AWS. In the subsequent phases, the CAPI provider will be tested with HCP OCP.

Goals (aka. expected user outcomes)

1. Create a Blog 

Requirements (aka. Acceptance Criteria):

As a cluster-admin or SRE I should be able to configure Karpenter with OCP on AWS. Both cli and UI should enable users to configure Karpenter and disable CAS.

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Out of Scope

Creating a multi-provider cost/pricing operator compatible with CAPI is beyond the scope of this Feature. That may take more time.

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

• Karpenter.sh is an open-source node provisioning project built for Kubernetes. It is designed to simplify Kubernetes infrastructure by automatically launching and terminating nodes based on the needs of your workloads. Karpenter can help you to reduce costs, improve performance, and simplify operations.
• Karpenter works by observing the unscheduled pods in your cluster and launching new nodes to accommodate them. Karpenter can also terminate nodes that are no longer needed, which can help you save money on infrastructure costs.
• Karpenter architecture has a Karpenter-core and Karpenter-provider as components. 
  The core has AWS code which does the resource calculation to reduce the cost by re-provisioning new nodes.