-
Notifications
You must be signed in to change notification settings - Fork 964
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
Delay in Pod Scheduling After Scale-Up Action #7063
Comments
How quickly are you expecting the pods to get scheduled? Pod would start running only when the capacity is provisioned for it to run. And that could take time, but that's not something controlled by Karpenter. |
Before Karpenter, it takes less than a second. |
Any help? |
Has been issue been resolved? |
Please, share with us the output of this command: |
This is the output of the command above, i removed sensitive data |
Description
Observed Behavior:
Pods are scheduled approximately 30 seconds after a scale-up action.
Expected Behavior:
I want the pods to be scheduled immediately after the scale-up action.
Reproduction Steps (Please include YAML):
Versions:
kubectl version
):Client Version: v1.28.2
Server Version: v1.29.7-eks-a18cd3a
The text was updated successfully, but these errors were encountered: