Skip to main content
NetApp Knowledge Base

Trident-operator incorrectly processes the imageRegistry parameter in the TridentOrchestrator resource

Views:
93
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

Trident 25.02

Issue

  • In Trident 25.02 the trident-operator incorrectly processes the imageRegistry parameter in the TridentOrchestrator resource.
  • Event entries for the affected pod:

Type     Reason         Age                    From               Message
  ----     ------         ----                   ----               -------
  Normal   Scheduled      5m34s                  default-scheduler  Successfully assigned kube-system/trident-node-linux-ftwmt to pool3-bm08s1-eph
  Normal   Pulling        5m34s                  kubelet            Pulling image "registry.eccd.local:5000/trident:25.02.0-7a8f590a"
  Normal   Pulled         5m33s                  kubelet            Successfully pulled image "registry.eccd.local:5000/trident:25.02.0-7a8f590a" in 972ms (972ms including waiting). Image size: 77266169 bytes.
  Normal   Created        5m33s                  kubelet            Created container: trident-main
  Normal   Started        5m33s                  kubelet            Started container trident-main
  Warning  InspectFailed  4m37s (x9 over 5m33s)  kubelet            Failed to apply default image tag "registry.eccd.local:5000/": couldn't parse image name "registry.eccd.local:5000/": invalid reference format
  Warning  Failed         4m37s (x9 over 5m33s)  kubelet            Error: InvalidImageName
  Warning  Unhealthy      32s (x45 over 5m13s)   kubelet            Readiness probe failed: HTTP probe failed with statuscode: 503

 

 

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.