Red Hat Bugzilla – Bug 1371309
enable pods-per-core and max-pods in node configuration
Last modified: 2017-03-08 13:43 EST
Description of problem: In the kubernetes 1.3 cycle, we added a feature to get away from a single max-pods value. https://github.com/kubernetes/kubernetes/pull/25813 "pods-per-core" is a simple scaling factor that allows us to get past the previous limit of 110 on larger systems. OpenShift should lay down a config like so (via installer): --pods-per-core=10 --max-pods=250 Which, when compared with openshift 3.2 max-pods=110, the effective behavior of the new pods-per-core algorithm: For 1-10 cores, max-pods is reduced For 11+ cores, max-pods is increased Examples: 8 cores: 8 cores * pods-per-core(10) = 80 80 < max-pods, so the limit is 80 pods. 16 cores: 16 cores * pods-per-core(10) = 160 160 < max-pods, so the limit is 160 pods. 32 cores * pods-per-core(10) = 320 320 > max-pods, so max-pods wins and the limit is 250
Verified, Fixed. openshift v3.4.0.19+346a31d kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 1. --pods-per-core=10 Capacity: alpha.kubernetes.io/nvidia-gpu: 0 cpu: 2 memory: 3881932Ki pods: 20 Allocatable: alpha.kubernetes.io/nvidia-gpu: 0 cpu: 2 memory: 3881932Ki pods: 20 2. --pods-per-core=0 Capacity: alpha.kubernetes.io/nvidia-gpu: 0 cpu: 2 memory: 3881932Ki pods: 250 Allocatable: alpha.kubernetes.io/nvidia-gpu: 0 cpu: 2 memory: 3881932Ki pods: 250
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0066