-
Notifications
You must be signed in to change notification settings - Fork 68
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
chore(armclient): removing 429 sdk retries in favor of controller retries #13
Conversation
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.
/test
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.
Approved but we should make sure we have test coverage that demonstrates that the controller-runtime loop-based backoffs do the right thing here. Do we?
Fixes #
Description
Karpenter is a reconciler, and will retry the scale up or delete request if it fails. Also note it only retries on 429 and some other options by default.
Instead of retrying with SDK we should retry with karpenter, and if we need additional retry flexiblity with backoff for throttling aim to get this change into karpenter core.
How was this change tested?
Scale up scale down
make az-presubmit
e2etests
Does this change impact docs?
Release Note