-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
e2e test for memory scaler #2646
Conversation
Signed-off-by: Ritikaa96 <[email protected]>
Signed-off-by: Ritikaa96 <[email protected]>
Signed-off-by: Ritikaa96 <[email protected]>
Hi @tomkerkhove , @JorTurFer |
/run-e2e memory.test.ts |
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.
Hi @Ritikaa96
First, thanks a lot for this ❤️
There are some notation inconsistencies, I have suggested 2 changes but you should review all the places where it happens.
Related with the flow, I'd propose to set less resources to ensure the scaling process (1% instead of 5% for example) and also I'd propose to instead of deleting the first SO and creating another one totally different, patching current SO to update the value. You could achieve it basically creating a variable with the SO template and calling it twice with different parameters to update it.
WDYT?
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.
Thanks for this, @JorTurFer have some great comments.
Signed-off-by: Ritikaa96 <[email protected]>
Signed-off-by: Ritikaa96 <[email protected]>
/run-e2e memory.test.ts |
Hi @JorTurFer , Done with the changes, Thanks for the suggestions. PTAL. |
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! ❤️
Only 1 small nit about one variable
Signed-off-by: Ritikaa96 <[email protected]>
Hi @JorTurFer , I apologize for the delay , was stuck because of an emergency. I corrected the variable PTAL. |
/run-e2e memory.test.ts |
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 this, let's wait till e2e passes
Could you update the changelog @Ritikaa96 ? |
Sure |
Signed-off-by: Ritikaa96 <[email protected]>
@JorTurFer @zroubalik PTAL |
This PR add E2E tests for memory scaler
Checklist
Fixes #2220