-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.14.z, 4.15.z
-
Important
-
None
-
False
-
Description of problem:
As per Red hat official documentation [-], The default maximum number of pods per node is 250. However when checked in the test cluster, observed more than 250 pods scheduled per node in the cluster. [-] https://docs.openshift.com/container-platform/4.14/scalability_and_performance/planning-your-environment-according-to-object-maximums.html#cluster-maximums-major-releases_object-limits
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
Test in a cluster 3 master and 3 worker nodes 1. Create a new project : $ oc new-project test 2. Create new application : $ oc new-app httpd 3. Increase the pod replica to 900 4. Check the number of pods per node : $ oc get pods -A -o wide | grep -i node-name | wc -l
Actual results:
As per documentation, the maximum number of pods can be scheduled per node is 250. In a test cluster , pods more than the default value are scheduled per node ~~~ $ oc get pods -o wide | grep -i worker-0 | wc -l 270 ~~~
Expected results:
If the default value of pods to get scheduled per node is changed, the documentation should be updated and must have the correct details.
Additional info:
Checked the pods per node : [quickcluster@upi-0 ~]$ oc get pods -A -o wide | grep -i worker-0 | wc -l 30 [quickcluster@upi-0 ~]$ oc get pods -A -o wide | grep -i worker-1 | wc -l 18 [quickcluster@upi-0 ~]$ oc get pods -A -o wide | grep -i worker-2 | wc -l 31 Created new project : $ oc new-project test Created new application : $ oc new-app httpd Edited deployment and checked the replicas to 900 Checked the pods per node : [quickcluster@upi-0 ~]$ oc get pods -A -o wide | grep -i worker-2 | wc -l 256 [quickcluster@upi-0 ~]$ oc get pods -A -o wide | grep -i worker-0 | wc -l 270