Abstract: Generally described, one or more aspects of the present application relate to scaling a cluster of compute capacity used to execute containerized applications or tasks. For example, a waiting area can be maintained, in which tasks that are requested to be executed in a cluster but are not able to be accommodated in the cluster due to the cluster not having sufficient compute capacity usable to execute such tasks are stored. The scaling of the cluster can be performed based on the characteristics of the tasks in the waiting area, such that the cost associated with adding too much compute capacity to the cluster can be reduced, while also reducing the time it takes to reach the desired level of compute capacity that can accommodate all of the requested tasks.

Abstract: Generally described, the present application relates to providing a container orchestration service (“service”) that can automatically detect and terminate a failed deployment and automatically roll back to a previous healthy deployment. For example, the service may receive a request to deploy a new user code onto one or more compute instances usable to execute the new user code, where the new user code is an updated version of an old user code to be replaced by the new user code. The service may then attempt to execute a plurality of instances of the new user code on the one or more compute instances, determine, prior to replacing all instances of the old user code to be replaced by the plurality of instances of the new user code, that the deployment of the new user code has satisfied a failed deployment condition, and terminate the deployment of the new user code.