Skip to content

OSDOCS-17666: Adding UI procedure for Capacity Reservations (ROSA HCP) #103902

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
otikhomi wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −1
Open

OSDOCS-17666: Adding UI procedure for Capacity Reservations (ROSA HCP) #103902

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions modules/creating-a-machine-pool-ocm.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,15 @@ ifdef::openshift-rosa,openshift-rosa-hcp[]
. Optional: Configure *Root disk size*.
endif::openshift-rosa,openshift-rosa-hcp[]

ifdef::openshift-rosa-hcp[]
. Optional: Add reserved capacity to your machine pool.
.. Select a *Reservation Preference* from the list. Valid preferences include:
... *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.
... *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.
... *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.
.. 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.
endif::openshift-rosa-hcp[]

. Optional: Add node labels and taints for your machine pool:
.. Expand the *Edit node labels and taints* menu.
.. Under *Node labels*, add *Key* and *Value* entries for your node labels.
Expand Down
2 changes: 1 addition & 1 deletion rosa_cluster_admin/rosa_nodes/rosa-managing-worker-nodes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Using Capacity Reservations on machine pools in {product-title} clusters has the
* You cannot use autoscaling on a machine pool with configured Capacity Reservations.
* You cannot upgrade a machine pool with configured Capacity Reservations.

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}].
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}].
endif::openshift-rosa-hcp[]

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