-
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
feat: supporting additional handing for TotalRegionalCores quota error, and adding better customer facing error messages on nodeclaim #45
Conversation
@juan-lee Let me know if you think this leads to a better experience in more clearly communicating you hit TotalRegionCores errors! |
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.
LGTM, mostly minor feedback in comments. Could we also have tests for these cases? Could follow example in 58586db
535a1b7
to
99d8a74
Compare
…r, alongside adding better customer facing error messages for the controller errors that end up in the nodeclaim
Co-authored-by: Alex Leites <[email protected]>
style: removing lint exception rule
f734a32
to
089d0a7
Compare
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
Co-authored-by: Alex Leites <[email protected]>
Co-authored-by: Alex Leites <[email protected]>
Co-authored-by: Alex Leites <[email protected]>
Co-authored-by: Alex Leites <[email protected]>
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
Co-authored-by: Alex Leites <[email protected]>
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
Fixes #
Description
This PR adds support for TotalRegionalCores errors and makes it more apparent for the customer that this is the root cause of the problem for why their scale up stopped.
This also modifies the code to use a less generic check for subscription level quota errors, and specifically only marking instances as unavailable if we see a SKUFamily quota error instead of just all subscription level quota errors.
We also are only logging the Azure Errors and are returning better customer facing errors in this case since they will be viewed in the nodeclaim.
How was this change tested?
Does this change impact docs?
Release Note