Skip to content

Commit 997d2f1

Browse files
committed
OSDOCS-17666: Adding UI proc for Capacity Reservations (ROSA HCP)
1 parent e6b1376 commit 997d2f1

File tree

2 files changed

+10
-1
lines changed

2 files changed

+10
-1
lines changed

modules/creating-a-machine-pool-ocm.adoc

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -93,6 +93,15 @@ ifdef::openshift-rosa,openshift-rosa-hcp[]
9393
. Optional: Configure *Root disk size*.
9494
endif::openshift-rosa,openshift-rosa-hcp[]
9595

96+
ifdef::openshift-rosa-hcp[]
97+
. Optional: Add reserved capacity to your machine pool.
98+
.. Select a *Reservation Preference* from the list. Valid preferences include:
99+
... *None* is the default value. The instance doesn't use a Capacity Reservation even if one is available. The instance runs as an EC2 On-Demand instance. Choose this option when you want to avoid consuming purchased reserved capacity and use it for other workloads.
100+
... *Open*: The instance can run in any `open` Capacity Reservation that has matching attributes (instance type, platform, AZ, or tenancy). Choose this option for flexibility: if a reservation isn't available, the instance can use regular unreserved EC2 capacity.
101+
... *CR only* (capacity reservation only): The instance can only run in a Capacity Reservation or Capacity Reservation group. If capacity isn’t available, the instance fails to launch.
102+
.. Add a *Reservation ID*. You get an ID in the `cr-<capacity_reservation_id>` format when you purchase a Capacity Reservation from AWS. The ID can be for both On-Demand Capacity Reservations or Capacity Blocks for ML.
103+
endif::openshift-rosa-hcp[]
104+
96105
. Optional: Add node labels and taints for your machine pool:
97106
.. Expand the *Edit node labels and taints* menu.
98107
.. Under *Node labels*, add *Key* and *Value* entries for your node labels.

rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Using Capacity Reservations on machine pools in {product-title} clusters has the
3232
* You cannot use autoscaling on a machine pool with configured Capacity Reservations.
3333
* You cannot upgrade a machine pool with configured Capacity Reservations.
3434
35-
To create a machine pool with a Capacity Reservation, see xref:../../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_machine_pools_cli_capres_rosa-managing-worker-nodes[Creating a machine pool with Capacity Reservations using the {rosa-cli}].
35+
You can create a machine pool with a Capacity Reservation using either xref:../../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_machine_pools_ocm_rosa-managing-worker-nodes[{cluster-manager}] or xref:../../rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc#creating_machine_pools_cli_capres_rosa-managing-worker-nodes[the {rosa-cli}].
3636
endif::openshift-rosa-hcp[]
3737

3838
include::modules/creating-a-machine-pool.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)