Failed to pull zookeeper image from private registry

Installed the apache/solr helm chart and override to pull the zookeeper image from our private registry with the command below:
helm install example apache-solr/solr --version 0.7.1 --set zk.provided.image.repository=my-registry.com.au/myuser/my_solrzookeeper --set zk.provided.image.tag=0.1.379 --set zk.provided.image.imagePullSecret=my-docker-registry-key

It failed to pull the zookeeper image from our private registry with error "no basic auth credentials" :
" Warning Failed 10s kubelet Failed to pull image "my-registry.sandstone.com.au/myuser/my_solrzookeeper:0.1.379": rpc error: code = Unknown desc = Error response from daemon: Head "https://my-registry.sandstone.com.au/v2/myuser/my_solrzookeeper/manifests/0.1.379": no basic auth credentials"

It appears the provided pull secret "my-docker-registry-key" is ignored and not sent to the private registry.

However, the solrcloud image can be pulled successfully from our private registry with the command below using the same pull secret:
helm install example apache-solr/solr --version 0.7.1 --set image.repository=my-registry.sandstone.com.au/myuser/my_solrcloud --set image.tag=0.1.3464 --set image.imagePullSecret=my-docker-registry-key

No source file or test is named. Start by inspecting the Helm chart templates and values for the provided ZooKeeper image, then compare its imagePullSecret handling with the working SolrCloud image path. Done means the configured pull secret is used when pulling the ZooKeeper image from a private registry, with a regression check if the chart has relevant tests.

Written by the indexing model from the issue text.