Unexpected nodeclaim consolidation

[Lily922]

Observed Behavior:
If all instance types of nodepools are unavailable(s.nodeClaimTemplates is empty), an existing nodeclaim will be misjudged as being consolidated. Because all pods on this node were incorrectly determined to be reschedulable to other nodes.

karpenter/pkg/controllers/provisioning/scheduling/scheduler.go

Line 288 in 1db5097

for _, nodeClaimTemplate := range s.nodeClaimTemplates {

If s.nodeClaimTemplates is empty, it means that a new nodeClaim cannot be created and an error should be returned.

[k8s-ci-robot]

This issue is currently awaiting triage.

If Karpenter contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.