Setting a realistic CPU limit on a Java OpenShift pod radically extends its start-up time

Issue

• Monitoring a Java-based application on OpenShift over its lifetime reveals a peak CPU usage of, for example, 0.1 cores. However, setting a CPU limit in this region has the effect that the pod takes minutes to start up.
• Most likely this problem will be observed on all OpenShift platforms, with all Java versions.