Helm chart creates the imagePullSecret list entry without creating the secret itself

Issue

• A secret gets added through helm charts as secured-cluster-services-main to the imagePullSecret list but it's not actually creating this secret.
• This is triggering a lot of warning messages in the logs

atomic-openshift-node: W0816 11:26:32.483704 6370 kubelet_pods.go:846] Unable to retrieve pull secret stackrox/secured-cluster-services-main for stackrox/collector-42dq6 due to secrets "secured-cluster-services-main" not found. The image pull may not succeed.

• Tested same through an Operator deployment:

$ oc adm node-logs --role=master -u kubelet | grep secured-cluster-services-main | tail
Jan 31 14:04:05.777667 hyperkube[1561]: I0131 14:04:05.777632    1561 kubelet_pods.go:895] "Unable to retrieve pull secret, the image pull may not succeed." pod="stackrox/collector-55jv7" secret="" err="secret \"secured-cluster-services-main\" not found"