Hypershift NodePools currently don't expose any status information regarding capacity reservations. For example, if a nodepool upgrade is attempted for a nodepool with an expired capacity reservation, the nodepool status still reflects a Ready state even in the case that new instances fail to provision due to the expired reservation.

    n/a (hyperhift operator)

    Easily reproducible by provisioning a nodepool with a capacity reservation that has expired.

    1. provision an HCP cluster.
    2. provision an AWS capacity reservation set to expire shortly (say 10 minutes)
    3. provision a nodepool with a capacity reservation ID value set to that reservation.
    4. after the reservation has expired, attempt to upgrade the nodepool and note the status.
    

    nodepool status is Ready

    nodepool status should reflect a non-Ready state