Skip to main content
NetApp Knowledge Base

Trident pods show CrashLoopBackOff or ImagePullBackOff after redeployment

  1. Last updated
  2. Save as PDF
Views:
113
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

Trident for Kubernetes/Openshift
Trident Protect 23.01.0 up to 26.02.0

Issue

Installation of pods is showing CrashLoopBackOff or ImagePullBackOff

For trident-protect-controller, the following error can be seen:

Failed to pull image "gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0": unable to pull image or OCI artifact:
pull image err: initializaing docker://gcr.io/kubebuilder/kube-rbac-proxy:v0.16.0: reading manifest c0.16.0 in
gcr.io/kubebuilder/kube-rbac-proxy: manifest unknown: Failed to fetch "v0.16.0": artifact err: get manifest:
build image source: reading manifest v0.16.0 in gcr.io/kubebuilder/kube-rbac-proxy: manifest unknown: Failed to fetch "v0.16.0".

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.