https://docs.google.com/document/d/1ID_IhXPpYY4K3G_wa1MYJxOb3yz5FYoOj3ONSkEDsZs/edit?tab=t.0#heading=h.yvv1wy2g0utk
Goal
- Define upgrade criteria for Karpenter Nodes (E.g. follow the control plane, this can be configurable at the HC level so the services can make their choice)
- Implement it relying on native Drift and Consolidation.
Why is this important?
- Reduce operational burden
Scenarios
- With AutoNode via karpenter the Service is authoritative to manage upgrades of karpenter Nodes.
- We need to agree on 1..N criteria/strategies. Possibly expose them in the HC API and let them be driven via Drift/Consolidation. Known caveats: in the current prototype everytime the ignition token is rotated would cause drift as a side effect. We'll need to either make it configurable or somehow transparent for drift
- ...
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)
- ...
Previous Work (Optional):
- …
Open questions:
- …
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>
Epic
Major
