Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

StatefulSet pod not restarted after pod eviction timeout

Views:
326
Visibility:
Public
Votes:
0
Category:
netapp-hci
Specialty:
solidfire
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

Issue

  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)

 

Scan to view the article on your device
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support