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

Goal

• Validate the implementation details are prod ready before removing the feature gate

Why is this important?

• …

Scenarios

• Revisit Default ec2Class
• Revisit karpenter IAM policy
• Consider vendoring karpenter instead of using unstructured types
• Consider manage the userdata programatically instead of using NodePool API
• Revisit rbac and watchers
• Last time I checked, karpenter was failing to allocate OCP workloads because of a conflicting label.
  https://github.com/kubernetes-sigs/karpenter/issues/1046#issuecomment-2578291462
  https://github.com/kubernetes-sigs/karpenter/pull/1908

• Remove feature gate

1. ...

Acceptance Criteria

• Dev - Has a valid enhancement if necessary
• CI - MUST be running successfully with tests automated
• QE - covered in Polarion test plan and tests implemented
• Release Technical Enablement - Must have TE slides
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions:

1. …

Done Checklist

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