Description of problem (please be detailed as possible and provide log snippests): RFE: When cluster node resources are already consumed and if user/customer want to create more pods then there should be WARN to add new pods or a suggestion to scale worker nodes to cluster. During manual testing observed this problem. When there is less resources in the nodes, new app pod creations were slow and sometime app pods will move to error state due to insufficient resources. Additional info: NA
not 4.3 material ==> to 4.4
@Nishanth, is this something we could address in the console?
This is default OCP behaviour. The platform tries to accommodate as many as pods that can be run. It's not possible to anticipate a pod CPU/Memory requirement until the deployment is created, and then the system checks if it can schedule the pod or not. There are ways the admins ease out their jobs by defining the number of maximum pods that can be scheduled on a node etc. But it is purely up to the admins on how they want to use their OCP cluster. Moreover, there are node events such as InsufficientFreeCPU & InsufficientFreeMemory to notify admins and many more (https://docs.openshift.com/container-platform/4.4/nodes/clusters/nodes-containers-events.html). In terms of alerting, there are alerts related to overcommitting of CPU and Memory: KubeCPUOvercommit & KubeMemOvercommit. Thus it is up to the OCP admin on how they want to manage their resources. Also, IMHO this is not a bug and certainly not an OCS bug.
Also the Node listing page on console has indications when memory/Disk/PID pressures are detected and displays the per node based utilization. So the point here that we believe that ocp has already implemented the necessary functionalities to warn the administrator well in advance.Hence I am closing the Bz. If you are expecting more, please re-open, explain what you are looking for and move Bz to OCP