-
Notifications
You must be signed in to change notification settings - Fork 43
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
Abnormal Time Between disruption runs #191
Labels
area/consolidation
Issues or PRs related to consolidation
area/deprovisioning
Issues or PRs related to deprovisioning
kind/bug
Categorizes issue or PR as related to a bug.
Comments
Controller logs for that nodeclaim that was problematic and possibly related. I could be way off base here as well
|
Bryce-Soghigian
added
area/consolidation
Issues or PRs related to consolidation
area/deprovisioning
Issues or PRs related to deprovisioning
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/bug
Categorizes issue or PR as related to a bug.
and removed
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
labels
Mar 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/consolidation
Issues or PRs related to consolidation
area/deprovisioning
Issues or PRs related to deprovisioning
kind/bug
Categorizes issue or PR as related to a bug.
Version
Karpenter Version: v0.3.0
__Karpenter Core Version: v0.33.1
Kubernetes Version: v1.27.9
Expected Behavior
We should ideally never see these logs as seeing a 15 minute delay in disruption breaks the scale down SLOs we promise.
Actual Behavior
When running long running deployments, every couple of days, we will see some abnormal time of runs for all of the disruption actions. Note that we do see some garbage collection of an instance shortly before we see all of the abnormal consolidation errors. Since TTL is 15m for GC, it might be possible that there is some conflict there.
We should look into
general-purpose-hcdgt
created.Steps to Reproduce the Problem
Unsure how to repro, need to dig further to find the RCA for this issue.
Resource Specs and Logs
Separating logs as they are too verbose and long github says maximum characters reached
Community Note
The text was updated successfully, but these errors were encountered: