メインコンテンツへスキップ

Kubernetesノードが予期せず停止した後、trident-controllerポッドが自動的に起動しない

  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 ポッドはTerminating状態のまま無期限に残ります
  • 別のノードで起動しようとする新しい trident-controller ポッドが 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.