-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unschedulable: 0/2 nodes are available: 2 Insufficient cpu. #706
Comments
This is a message from k8s. It says that you have two nodes in your cluster but none of them meet the requirements of requested CPUs. |
@SinaChavoshi - please scale out the cluster by adding more nodes to the pool, or setup auto-scaling for the node pool. @jlewi - should we consider setting up auto-scaling automatically in the 1-click deploy app? |
Autoscaling should already be enabled: My hunch is @SinaChavoshi is requesting a single pod with 20 CPUs. The current default VM type is 8 CPU This was by design to try to fit into the free tier. There are two options here
It looks like auto-provisioning should be enabled: And should be able to provision larger nodes. @SinaChavoshi Which version of Kubeflow are you using? I think we only turned on auto-provisioning in 0.4. If you look at the K8s events for the resource that isn't getting scheduled (e.g. the pod) it should provide more information about why autoscaling didn't kick in. |
Resolving since there does not seem to be any next action to take. Please re-open if something else is needed. |
…r. (kubeflow#703) (kubeflow#706) * Upgrade Tekton to 0.27 for pipelineloop controller. (kubeflow#703) * Upgrade Tekton to 0.27 for pipelineloop controller. (kubeflow#703) * Update pipelinelooprun.go
The error message for resource shortage is incorrect. In this instance i was requesting 20 cpus where my cluster has a max limit of 10.
https://screenshot.googleplex.com/yvuBNnYqn0p
The text was updated successfully, but these errors were encountered: