-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
- Multiple instance types configured in the same MachinePool
2. What is the nature and description of the request?
- Customer would like to have the possibility to configure multiple instance types for the same MachinePool, similar to how managed node groups work in AWS EKS, as seen here: https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html (more details here -> https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html#:~:text=On-Demand%20capacity.-,for%20example,-%2C%20you%20might%20specify )
For example, you might specify three instance types in the following order: c5.large, c4.large, and c3.large. When your On-Demand Instances are launched, the managed node group fulfills On-Demand capacity by starting with c5.large, then c4.large, and then c3.large
3. Why does the customer need this? (List the business requirements here)
- The current approach for the customer relies on on-demand nodes, and restricting each node pool to a single instance type introduces an availability risk. When that particular instance type is unavailable, cluster autoscaler may be unable to scale out, which could impact service reliability
4. List any affected packages or components.
- ROSA MachinePools