Epic Goal

• Document tests taken on OCP self-managed in SPLAT-1416 to autoNode (via Karpenter) feature once it's exposed in the hypershift.HostedCluster API as --tech-preview before is exposed in ocm. The document targets to hand of the knowledge to QE teams validate the product
• Identify if implemented automation developed in kube-burner[1] to support scaling tests on OCP self-managed need to be ported to upstream (need to sync with Perf & Scale), so Perf & Scale teams can evaluate the performance gaps
• Identify any UX gaps for autoNode feature

Feature proposal is described here: https://docs.google.com/document/d/1ID_IhXPpYY4K3G_wa1MYJxOb3yz5FYoOj3ONSkEDsZs/edit?tab=t.0#heading=h.yvv1wy2g0utk

Why is this important?

Scenarios

1. ...

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. ...

Previous Work (Optional):

1. Here are the Karpenter setup steps used by Mike to build the data/presentation comparing CAS with Karpenter
2. Here are the steps to run the tests for each "profile"

Open questions::

1. Should we need to create a PR in kube-burner with profiles added for autoscaling developed when testing in self-managed?
2. What would be the baseline to validate the performance?
3. In self-managed we've created 4 profiles: homogeneous and heterogeneous instance types, and spot and OD for each. Do we need to document all of that, or just heterogeneous with OD and spot?

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>