Scaling strategy to limit number of Machine pending or provisioning #8808
Labels
area/machine
Issues or PRs related to machine lifecycle management
kind/feature
Categorizes issue or PR as related to a new feature.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
What would you like to be added (User Story)?
An an operator, I would like to control how fast new Machines are created when I create large clusters to avoid overwhelming controllers and infrastructure.
Detailed Description
I want a way to limit the number of Machines that are pending or provisioning. Currently, when creating large clusters we start out small and scale gradually to avoid issues. However, this could be easily automated and solved for all providers if built in to CAPI.
In the Bare Metal Operator we have a
PROVISIONING_LIMIT
for exactly this reason. It limits the number of BareMetalHosts that are provisioned simultaneously. Having something similar in CAPI would be very useful.I'm not sure where it would make sense to add this option though. It could be set on the Cluster, the KCP and/or MachineDeployment for example. to get granular control. Or it could be a flag for the controllers. What do you think would work best?
Anything else you would like to add?
No response
Label(s) to be applied
/kind feature
/area machine
The text was updated successfully, but these errors were encountered: