Karpenter considers nodes not owned by it for disruption

[george-zubrienko]

Description

Observed Behavior:
We have a system pool (autoscaling group) that hosts system pods and Karpenter itself. After upgrading to 1.0.8 from 0.37.6 I see a lot of events likes below for those nodes:

31 DisruptionBlocked: Cannot disrupt Node: state node doesn't contain both a node and a nodeclaim

I understand Karpenter will not disrupt this node, but the fact it actually considers it, even though it is not tagged by it, is major confusing.

Expected Behavior:

Nodes not owned by Karpenter should not be considered for disruption similar to pre-v1 versions

Reproduction Steps (Please include YAML):
Install Karpenter according to the quickstart guide and observe event emitted for nodes that host Karpenter itself.

Versions:

• 1.0.8
• Kubernetes Version (kubectl version): 1.29

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[jigisha620]

This is not necessarily a bug that was introduced in v1.0. The log itself is confusing and a fix has been added in this PR kubernetes-sigs/karpenter#1644.

[github-actions]

This issue has been inactive for 14 days. StaleBot will close this stale issue after 14 more days of inactivity.