-
Bug
-
Resolution: Done
-
Normal
-
None
-
premerge, 4.14
-
Quality / Stability / Reliability
-
False
-
-
None
-
Informational
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 274
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Customer finds for the equivalent settings for serializeImagePulls and maxParallelImagePulls in OpenShift Container Platform same as in Kubernetes.
As it is not mentioned in the official documentation.
According to the Kubernetes documentation, the default for SerializeImagePulls is true.
but the default value for SerializeImagePulls is False in OpenShift 3 and 4
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
Follow the below steps to configure serializeImagePulls and maxParallelImagePulls in openshift:
1. First of all label the machine config pool for that you want to set above parameters:
$ oc label mcp worker custom-kubelet=sysctl
2. Create a kubelet config :
$ vi kube.yaml
apiVersion: machineconfiguration.openshift.io/v1
kind: KubeletConfig
metadata:
name: set-max
spec:
machineConfigPoolSelector:
matchLabels:
custom-kubelet: sysctl
kubeletConfig:
maxParallelImagePulls: 3
In the above it is not required to specify serializeImagePulls: false, as it default value in openshift.
$ oc create -f kube.yaml
3. Verify that it is created successfully:
$ oc get kubeletconfigs.machineconfiguration.openshift.io
NAME AGE
set-max 14m
4. Verify at node level:
$ cat /etc/kubernetes/kubelet.conf | grep -i maxParallelImagePulls
"maxParallelImagePulls": 3,