Acceptance criteria

Utilize existing Capacity Reservation ID for a new or existing ROSA HCP Machine Pools.

All Capacity Reservation code should be behind a feature flag!

Cluster Details - Machine Pool tab

Updates to "Add HCP Machine Pool" modal

Add Capacity Reservation Preference and ID fields. 

Add the 'Reservation Preference' field to the Overview tab:

      Capacity Reservation
          Reservation Preference: [None | Open | CR only |v]  //  dropdown. 'None' is default
          Reservation Id: [cr-....]                                               //  only enabled when 'CR only'

• Note: CR section & ID field should've been added via https://issues.redhat.com/browse/OCMUI-3832
• If cluster version selected is < 4.19 then disable Capacity Reservation fields and show disabled tooltip as to why disabled and how to enable ("Select cluster version >= 4.19")

• Autoscaling is targeted to be supported in M2.

Updates to "Edit HCP Machine Pool" modal

• If Capacity Reservation set:
  • Capacity Reservation fields are read-only/non-editable (can't change existing Capacity Reservation settings)
  • User cannot edit CR fields once set.  If they want to change the Capacity Reservation, they need to delete and recreate the machine pool.
• If Capacity Reservation not set on an existing machine pool:
  • Capacity Reservation fields are editable.
  • Same behavior as the "Add Machine Pool" modal
• Check AWSCapacityReservations, do not show CR fields is no capability
• Show Tech Preview badge

Machine pools table 

1. In the HCP Machine Pool tab, for a machine pool, show in expanded row:
   Capacity Reservation (Technology preview)
      Reservation Preference: Open | CR only | None
      Reservation Id: CR-AGEABH35TG
2. Check AWSCapacityReservations, do not show CR fields is no capability
3. Show Tech Preview badge
4. Upgrading of machine/node pools is targeted to be supported in M2

Out of scope

• Support for ROSA Classic, OSD on AWS.
• Use Capacity Reservation during cluster creation (on day-1 machine pool)
  • Customer is responsible for ensuring to create clusters in the region where Capacity Blocks are supported
• Once a machine pool is set to Capacity Reservation, once cannot (at this time) remove the capacity reservation.  DDR indicates one must delete and recreate the MP w/o Capacity Reservation.