Skip to main content
NetApp Knowledge Base

StatefulSet pod not restarted after pod eviction timeout

Last Updated:

Applies to

  • RedHat OpenShift 3.11 cluster
  • Netapp HCI
  • StatefulSet resource defined in the OpenShift cluster
  • Netapp Trident plugin
  • Persistent Volume Claim (PVC)
  • Persistent Volume (PV)
  • Kubernetes cluster


  1. A PVC was submitted to the Openshift cluster and Trident created the associated PV in Element
  2. Deployed a StatefulSet resource (with one replica pod) in the RedHat OpenShift cluster
  3. The pod template yaml file in the StatefulSet resource contains the PVC created, so its bound PV will be attached and mounted in the StatefulSet pod replica
  4. When the node where the StatefulSet pod has been scheduled to, fails for any reason, the pod is not restarted in another worker node in the same OpenShift cluster, when the pod eviction timeout has been reached (by default set to 5 minutes)


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.