-
Notifications
You must be signed in to change notification settings - Fork 983
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
test: Add unit test to validate the instancetype cache #5917
Conversation
✅ Deploy Preview for karpenter-docs-prod canceled.
|
890fe97
to
7cdc5ac
Compare
Pull Request Test Coverage Report for Build 8635855489Details
💛 - Coveralls |
bd72ea8
to
bd387e8
Compare
f20cb17
to
7b915b1
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.
Is there some sort of reflection we can do to make sure that each of the values that are added into the InstanceTypesProvider.List() has a table entry? It seems like this does the job, but there's no test that would fail if someone just finds + replaces all the instances of the List() function definition to add a new parameter.
2f1ac4e
to
66f4c0f
Compare
77fe86d
to
2b2dde5
Compare
2b2dde5
to
05d8d34
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.
LGTM 🚀
Fixes #N/A
Description
Add unit test to validate the instancetype cache will give different set of instance type based on input
The tested value currently are
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.