Reservations for classic worker node costs

Deprecation timeline

Migrating workloads from reservations

To prevent loss of service, you must create non-reserved worker pools and migrate your workloads before each reservation contract expires. If a contract expires while you have more worker nodes in use than the remaining reservation capacity, worker nodes that exceed the capacity are deleted automatically.

1. Find your active reservation contracts and note the expiration date of each one. The expiration date is your deadline for migrating any workloads that use that contract's worker nodes.

   1. Log in to the IBM Cloud Kubernetes Service reservations console.
   2. Click each reservation to view the contracts and their expiration dates in the Contracts section.

2. Create a new worker pool that does not use a reservation. For more information, see the documentation for your service.

   • Adding worker nodes to classic clusters in IBM Cloud Kubernetes Service
   • Adding worker nodes to classic clusters in Red Hat OpenShift on IBM Cloud

3. Migrate your workloads from the reserved worker pool to the new worker pool. Use labels or node selectors to reschedule your existing workloads to the new worker pool. [VERIFY: Confirm whether additional migration steps are recommended for this specific context.]

4. Delete the worker pools that use reservations after workload migration is complete.

About reservations

A reservation is an IBM Cloud resource that describes the flavor, location, and other details of worker nodes that you purchased. Contracts associated with a reservation are agreements to pay a fixed monthly amount for a set number of worker nodes for a 1 or 3 year term.

Reservations are available only for classic infrastructure worker nodes in multizone regions (MZRs). Worker pools that use reservations cannot use the cluster autoscaler add-on.

When a contract expires, your reservation is checked against remaining capacity from other active contracts. If you have more worker nodes in use than the remaining capacity, worker nodes that exceed the total capacity are deleted. To avoid unexpected deletions, scale down your worker pools before a contract ends to match the remaining reservation capacity.

You cannot modify the terms of a contract, such as the duration, number of worker nodes, or flavor. You can remove unneeded worker nodes from your clusters, but you cannot get a refund for unused capacity.

Reviewing reservation usage

You can review your IBM Cloud Kubernetes Service reservation usage and billing details.

Before you begin, make sure that you have the following roles in IBM Cloud IAM.

• Viewer platform access role for Kubernetes Service to view reservation usage details.
• Viewer platform access role for Account Management > Billing service to view billing details.

Reservation usage:

1. Log in to the IBM Cloud Kubernetes Service reservations console.
2. Review the Usage column to see how many worker nodes of the total amount are in use, such as 1 of 3 worker nodes.
3. Review the Clusters column to see how many clusters have worker nodes that use the reservation.

Billing details:

1. Log in to the IBM Cloud billing console.
2. From the navigation menu, click Usage.
3. From the Services table, find the Kubernetes Service row and click View plans.
4. From the plans table, find the row for your reservation name and click View details.
5. Review the details for the reserved worker nodes that are associated with the contracts of your reservation.

Next steps

• Add worker nodes to classic clusters in IBM Cloud Kubernetes Service
• Add worker nodes to classic clusters in Red Hat OpenShift on IBM Cloud
• Plan your cluster for high availability