跳转到主内容

K8s 节点意外停止后 trident-controller pod 不会自动启动

  1. 最后更新
  2. 另存为PDF
Views:
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

适用于

  • Trident
  • OpenShift
  • Kubernetes (K8s)
  • 具有高可用性 (HA) 控制平面的 OpenShift 或 Kubernetes 集群

问题

  • OpenShift 或 Kubernetes 节点意外停止后，该节点上之前的 trident-controller pod 将无限期处于 Terminating 状态
  • 尝试在另一个节点上启动的新 trident-controller pod 进入  CrashLoopBackOff 状态

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.