Feature #18113
Updated by Tom Clegg over 2 years ago
Instead of 0 (unlimited) we could start with values that are reasonable for a normal size production cluster / typical cloud account. MaxConcurrentInstanceCreateOps was invented to accommodate Azure limitations, but now that we have it, we might as well promote using it as a guard rail for all cloud providers. Perhaps 10 ops per second and 1 concurrent create op. Recommend raising to 20 concurrent create ops for Azure since it doesn't return the "create" response until the instance has booted. ops?