Hide Forgot
Document URL: https://docs.openshift.com/enterprise/3.1/admin_guide/overcommit.html#reserving-resources-for-system-processes Section Number and Name: Reserving Resources for System Processes Describe the issue: The documentation on how to implement this is very vague (how do I get the pod deployed), does not indicate if the pod will be a container on the node that is only visible by docker or if it will be a proper OSE pod, and it does not indicate what to start (service or reboot the whole node). Suggestions for improvement: Clarify all of these points, and indicate what to look for if the pod is not starting.
Have been playing with ose and trying to create the resource-reserver pod as is written in the documentation. I have not been able to have the pod created. I have dropped the yaml file under /etc/origin/node directory, restarted atomic-openshift-node.service service (many times). Nothing. Of course, running 'oc create -f resource-reserver.yaml' will create the pod. Maybe additional configuration of the node is required to have the running daemon read all yaml file with object specification and create them.
Ok, node-config.yaml has to be updated. Adding: kubeletArguments: config: - "/etc/origin/node" will read yaml files from /etc/origin/node. Once configure, resource-reserver pod is created as well.
Running 'oc delete resource-reserver-pod-id` will not delete the pod. If an operator wish to delete the pod, node-config.yaml has to be updated again. To e.g. kubeletArguments: config: - "" Or the resource-reserver.yaml has to be removed from /etc/origin/node.
Upstream PR [1]. [1] https://github.com/openshift/openshift-docs/pull/1892
PRs merged: https://github.com/openshift/openshift-docs/pull/1892#event-678832801 https://github.com/openshift/openshift-docs/pull/2193#event-678948098 Live: https://docs.openshift.com/enterprise/3.2/admin_guide/overcommit.html Moving to CLOSED CURRENTRELEASE.