-
Notifications
You must be signed in to change notification settings - Fork 150
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
Configure default cpuLimit and cpuRequest #796
Conversation
Signed-off-by: Vladyslav Zhukovskyi <vzhukovs@redhat.com>
Was it tested on RHPDS and the dogfooding environment? |
@ericwill it was tested on RHPDS, but for RHPDS meta.yaml for the theia-editor needs to be a bit modified. To provide cpuLimit: 1.5 and cpuRequest 0.5. Because there was a fix for 7.23 which provides correct cpu configuration conversion, but che on RHPDS is 7.20.2 As for dogfooding instance. I'm trying to get an access to this host. Will post results of check asap. |
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.
I also checked it on our internal dogfooding instance.
LGTM, but up to @ericwill
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.
Sorry, forgot to review this yesterday. LGTM.
What does this PR do?
Configure default values for
cpuLimit: 1500m
andcpuRequest: 500m
for next tag image.Signed-off-by: Vladyslav Zhukovskyi vzhukovs@redhat.com
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
eclipse-che/che#18565
How to test this PR?
Create a workspace from the provided devfile, workspace should be able to start.
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.