Feature Overview (aka. Goal Summary)  

As a cluster administrator, I want to use Karpenter on an  Self-managed OCP via web-console
Support ability to see nodeclasses, nodepools, and nodeclaims in the web-console.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

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.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

• Ability to enable AutoNode/Karpenter during installation and post-cluster installation
• Ability to run AutoNode/Karpenter and Cluster Autoscaler at the same time
• Use with an OpenShift cluster with Hosted Control Planes
• CAPI to enable/disable/configure AutoNode/Karpenter
• Have AutoNode/Karpenter perform data plane upgrades
• Designed for FIPS / FIPS compatible
• Enable cost effective mixed compute with auto-provisioning from/to zero
• Provide Karpenter metrics for monitoring and reporting purposes

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

• Migration guides from using CAS to Karpenter
• Performance testing to compare CAS vs Karpenter on ROSA HCP
• API documentation for NodePool and EC2NodeClass configuration

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>