Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
alysondeives opened this issue Feb 6, 2025 · 1 comment
Labels
enhancement New feature or request

Comments

@alysondeives
Copy link

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 tkatila added the enhancement New feature or request label Feb 7, 2025
@tkatila
Copy link
Contributor

tkatila commented Feb 7, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants