Skip to main content
NetApp Knowledge Base

trident-controller pod does not start automatically after K8s node unexpectedly stops

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

Applies to

  • Trident
  • OpenShift
  • Kubernetes (K8s)
  • OpenShift or Kubernetes clusters with a highly available (HA) control plane

Issue

  • After OpenShift or Kubernetes node unexpectedly stops, the previous trident-controller pod on that node remains in Terminating status indefinitely
  • A new trident-controller pod that attempts to start on another node enters CrashLoopBackOff status

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.