Skip to main content
NetApp Knowledge Base

TBE for Trident remains in terminating state, the TBC being offline

  1. Last updated
  2. Save as PDF
Views:
68
Visibility:
Public
Votes:
0
Category:
trident-kubernetes
Specialty:
snapx
Last Updated:

Applies to

Astra Trident for Kubernetes and Openshift

Issue

Attempting to delete an unused Trident Backend in the kubelet TBE definition, the TBE remains in terminating state and is not removed.
Checking the tridentctl get backend output, shows that the related backend is offline, or completely missing.

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.