Last Updated: 16 January 2026
Introduction
This article covers how reservations work in Crusoe Managed Kubernetes (CMK), both from instances and NodePools perspectives.
How Reservations Work on CMK
By default, any instances from any given cluster's NodePool will use any available reservation capacity in the Organization.
If there is no available reservation, or the reservations have run out of capacity, the new NodePool instances will be created with On-Demand pricing.
The above means that, by default, CMK will handle available reservations automatically so there's no need to manually link NodePools and/or NodePool instances to reservations.
Question 1: Can I link individual NodePool instances to specific reservations?
Answer
Since CMK manages reservations automatically based on available capacity, manually linking instances to reservations is not supported anymore.
Additional Resources
For additional information on reservations, see the reference below: