Skip to main content
NetApp Knowledge Base

Kubernetes Pods Stuck in Terminating/BackOff State When NetApp Storage Is Unavailable

  1. Last updated
  2. Save as PDF
Views:
13
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
SNAPX
Last Updated:

Applies to

  • NetApp ONTAP (All Flash FAS, AFF-C800, and similar)
  • Trident CSI Driver for Kubernetes
  • Kubernetes clusters using NetApp persistent volumes

Issue

Kubernetes pods that rely on NetApp persistent storage remain stuck in abnormal states (e.g., Terminating, BackOff) and cannot be gracefully deleted or recovered when the backend NetApp storage is offline (e.g., due to a controller panic and LUNs entering nvfail state).

Log Output/Symptom Examples:

  • Pods remain in Terminating state for extended periods.
  • Pods enter BackOff if volume mount attempts repeatedly fail.
  • Cluster events show failed volume unmounts or inaccessible storage.
  • Storage controller logs indicate LUNs in nvfail and backend services offline.

 

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.