karpenter has a disruption feature for drift detection which allows it to replace nodes that have configuration differences from the defined NodePool and NodeClass objects.

this spike is about researching how we can integrate karpenter's drift detection with openshift's node upgrade mechanisms.

Open Questions

• will we need to account for in-place upgrades?

DoD

• a draft enhancement describing how drift detection will work with autonode on hcp