-
Notifications
You must be signed in to change notification settings - Fork 51
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
Update the memory limits for the powervm-rmc
pods.
#180
Update the memory limits for the powervm-rmc
pods.
#180
Conversation
Welcome @kishen-v! It looks like this is your first PR to ocp-power-automation/ocp4-playbooks 🎉 |
e6056f9
to
dc36f93
Compare
/cc @pravin-dsilva |
dc36f93
to
4968b28
Compare
Signed-off-by: Kishen V <kishen.viswanathan@ibm.com>
4968b28
to
b6eecc5
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
@kishen-v did we test this out with a smaller configuration as well? |
Hi @yussufsh, yes. We had initially loaded these limits for the |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kishen-v, Prajyot-Parab, yussufsh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This PR has the updated limits for the
powervm-rmc
pod which prevents encountering theOOMKilled
and subsequentCrashLoopBackOff
errors on large compute nodes for the same.The change was tested on a node of size 64 Cores and 256GB of memory and the desired behaviour of the
powervm-rmc
pod was observed.