Skip to main content
NetApp Knowledge Base

Cluster wide pod rebuild from Kubernetes causes Trident's operator to become unusable

Last Updated:

Applies to

  • Trident 20.07.0, 20.10.0
  • Openshift 4.5.13, 4.5.18
  • Kubernetes 1.18


Since the pods are destroyed and created in a non-predetermined order, the orchestrator may find missing pods and attempt repair before the whole rebuild is finished.
The main error that can comes up during this is:
Warning FailedMount pod/trident-csi-<POD_ID> MountVolume.SetUp failed for volume "trident-csi-token-<POD_ID>" : secret "trident-csi-token-<POD_ID>" not found


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.
Scan to view the article on your device