Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
fix: properly garbage collecting orphaned network interfaces #642
base: main
Are you sure you want to change the base?
fix: properly garbage collecting orphaned network interfaces #642
Changes from all commits
5d7853b
4c3e8df
3a77d94
d595df5
4ad1738
d066fc5
c71f4dc
900c48d
cce9f3c
d7eb78c
97db74f
8867815
871aebd
a97ce3a
4f299d8
9d39576
85d84f5
c495b97
176c7f8
d8fa55b
a02263c
41319bf
e300439
8418208
ad84b51
aaccc95
fa14e9a
fdf3147
730b754
fe0c4a0
3d0b0b9
c0e4043
50d9455
f4f2e59
cfa1776
0ea44f4
d9d858a
d631e19
9d49d25
38666ed
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instance GC controller combines the errors and returns them, here they are only logged an never returned. Why the difference in behaviour?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried looking into the original pr to see if we got any rationality behind that: aws/karpenter-provider-aws#3405
Didn't see much.
We shouldn't be requeuing more frequently in the presence of errors. We should probably change that, if VM Deletion fails due to a TooManyRequests error, we can't retry until the quota window resets(After 5 minutes?)
2m might make some sense for vms as the volume of vms that need garbage collection is in most cases significantly lower than the volume of interfaces that need garbage collection.
We could try requeuing depending on the kind of error at different intervals.
If we see TooManyRequests Error wait 5 minutes to retry, if we see IsNicReservedForAnotherVM retry 3 minutes later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall it seems simpler to just not do all of that requeuing and come and optimize it later if we are optimizing for performance. For now just requeuing every 5 minutes seems to be fine.