Skip to main content
NetApp Knowledge Base

Trident Helm install fails with: <.Values.imagePullSecrets>: range can't iterate

Views:
27
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:
5/6/2025, 9:33:41 AM

Applies to

  • Astra Trident
  • Helm Installations using private, on-prem registry (no Internet access)

Issue

Background:
For environments that do not allow direct access to the internet, a private, harbor container can be set up to use an on-premise registry service. Since a typical deployment (connected to external registry) uses a standard registry secret type, a custom secret is created for an on-prem file (called 'regcred' in this example) with the following  data structure:

"Registery Domain Name" - <domain_name.local>
Username
Password

Issue:
From Trident documentation: Deploy Trident operator using Helm (Offline mode), running the following install command may produce an error:

# helm install trident-operator netapp-trident/trident-operator --version 100.2502.0 --create-namespace -n trident-system --set imageRegistry=domain_name_example.local/itdevops --set imagePullSecrets=regcred



Error: INSTALLATION FAILED: template: trident-operator/templates/serviceaccount.yaml:17:17: executing "trident-operator/templates/serviceaccount.yaml" at <.Values.imagePullSecrets>: range can't iterate over regcred

 

 

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.