Skip to main content
NetApp Knowledge Base

Trident pod is stuck in a crashloopbackoff state and is unable to be used

  1. Last updated
    Jun 9, 2025
  2. Save as PDF
Views:
11
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:
6/9/2025, 4:34:17 PM

Applies to

  • Trident

Issue

Trident pod is seen stuck in a crashloopbackoff state and is unable to be used as it is in an unhealthy state. The following errors are seen persistent even after manually deleting the pod and it being recreated.
 
LAST SEEN   TYPE      REASON      OBJECT                         MESSAGE
39m         Warning   Unhealthy   pod/trident-node   Readiness probe failed: HTTP probe failed with statuscode: 503
19m         Normal    Pulled      pod/trident-node   Container image "registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.1.0" already present on machine
2m11s       Warning   BackOff     pod/trident-node   Back-off restarting failed container driver-registrar in pod trident-node(a1234-4a234-44abc-bb11-abcd112345)

level=warning msg="Could not update Trident controller with node registration, will retry." error="failed during retry for CreateNode: could not log into the Trident CSI Controller: error communicating with Trident CSI Controller; Put \https://10.10.10.10:34571/trident/v1/node/nodename\: context deadline exceeded (Client.Timeout exceeded while awaiting headers)" increment=1m19.425781211s logLayer=csi_frontend requestSource=Internal workflow="plugin=activate"

 

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.