device plugin images (dsa, qat) fails to pull when defining a private registry on operator helm chart

[alysondeives]

Describe the bug There is an option to use a private registry in the intel-device-operator helm-chart:

https://github.com/intel/helm-charts/blob/intel-device-plugins-operator-0.30.0/charts/device-plugin-operator/values.yaml#L17

This will define a Secret so it is possible authenticate and download the images from the private registry https://github.com/intel/helm-charts/blob/intel-device-plugins-operator-0.30.0/charts/device-plugin-operator/templates/operator.yaml#L401

However, if we also deploy any device plugin helm-chart, such as dsa or qat, the images are not downloaded because it is not possible to authenticate to the private registry since no secret was created for them.

To Reproduce

• Create a private registry and upload all required images to it.
• Deploy intel-device-plugin operator helm-chart defining the private registry previously created
• Deploy dsa-device-plugin and/or qat-device-plugin. Notice that both plugin and init-container images will not be downloaded from the private registry

Expected behavior The device plugin and init container images should be downloaded from the private registry defined on intel-device-operator helm-chart.

Screenshots If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• OS version: Debian 11
• Kernel version: Linux 6.6
• Device plugins version: v0.30.0
• Hardware info: SPR with QAT and DSA

Additional context Add any other context about the problem here.

[tkatila]

thanks @alysondeives, we'll add this to our work queue. I would expect this to hit our next release (0.33.0) unless there are needs for a patch release.

[tkatila]

This is now possible with the 0.34.0 release. The secret that is passed on to the operator is also passed on to the plugin objects.