https://github.com/aws/karpenter-provider-aws/blob/fe32aaec924402ae9e1db93ccdd67d9893e7ce00/designs/metrics.md?plain=1#L6

Goal

• Let the karpenter-operator and karpenter to expose metrics
• Discuss with SRE and expose some of those in SRE grafana dashboards

Why is this important?

• AutoNode driven by karpenter is a different paradigm than mapi/capi driven. Usful monitoring it's critical for triaging issues

Scenarios

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>