Skip to main content
NetApp Knowledge Base

Trident image pulls from docker registry instead of our private registry

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

Astra Trident (versions 24.10 - 25.02.0)

Issue

  • Trident-operator incorrectly processes the imageRegistry parameter in the TridentOrchestrator resource. When an imageRegistry is specified, all CSI-sidecar containers in the Kubernetes manifest are set to use the image from the imageRegistry. However, the image names and tags are not correctly populated, leading to incorrect image references.
  • Image is pulled from docker rather than private image registry

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.