-
Notifications
You must be signed in to change notification settings - Fork 9
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 resource limits #102
Conversation
This prevents people from explicity setting memory or cpu request to 0 for their containers. While such pods will be the first to be kicked out when the cluster is low on resources, they will continue to run for free at other times. With this in place the scheduler will reject the container from running with an appropriate message to the user.
This sets it such that the CPU to Memory ratio aligns with our CPU SU definition of 1 CPU to 4 Gi of Memory. Note that I lowered the CPU limits and request instead of only increasing the memory.
The manifests are copy pasted into the nerc-ocp-config repo, so you need to change it here too https://github.com/OCP-on-NERC/nerc-ocp-config/blob/ad7ae587560af0845b1aac30ce6c06587325b92e/acct-mgt/base/configmaps.yaml#L52 |
@knikolla okay, thanks for pointing that out. I guess once we have agreed here on what the numbers should be I can update it in the other place too. |
Looks like microshift CI/CD failure is unrelated to this PR. |
The default container size aligns with our SU definitions and now there's a minimum size for a container. Related: CCI-MOC/openshift-acct-mgt#102
The default container size aligns with our SU definitions and now there's a minimum size for a container. Related: CCI-MOC/openshift-acct-mgt#102
The default container size aligns with our SU definitions and now there's a minimum size for a container. Related: CCI-MOC/openshift-acct-mgt#102
This PR addresses nerc-project/operations#602 and nerc-project/coldfront-plugin-cloud#108
Feel free to suggest any other defaults or mininum values.