-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Alternate approach to solve #8482 based on ideas from @moko-poi in PR #8547 #8684
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
Conversation
✅ Deploy Preview for karpenter-docs-prod ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Thanks @youwalther65 and @DerekFrank for following up on this! I'm totally fine with continuing this work in #8684 — it keeps the intent of #8547 while making the log order deterministic and preserving backward compatibility. Happy to close #8547 once this PR becomes the final implementation. |
|
Preview deployment ready! Preview URL: https://pr-8684.d18coufmbnnaag.amplifyapp.com Built from commit |
Pull Request Test Coverage Report for Build 19564760545Details
💛 - Coveralls |
a223670 to
d554049
Compare
DerekFrank
left a comment
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! Thanks for picking this up
Alternate approach to solve #8482 based on ideas from @moko-poi in PR #8547
Fixes #8482
Description
Adds FleetID to Karpenter controller logs in case of
InsufficientInstanceCapacityerror in EC2 CreateFleet API call.Moved logging out ofpkg/cache/unavailableofferings.gofuncMarkUnavailable.After offline discussion with @DerekFrank I moved logging back to
pkg/cache/unavailableofferings.gofuncMarkUnavailable, but now keep log item order backward compatible using approach here.How was this change tested?
Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.