Skip to main content
NetApp Knowledge Base

Object and image issues from failovers and failback operations on a trident protect installation in an Openshift cluster

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

Applies to

  • Trident Protect up to 25.10.0 to 26.02.1
  • Openshift (4.16) as Kubernetes environment

Issue

When providing DR between two Openshift clusters, some objects are not handled correctly:
  • Route objects are copied to the destination cluster, but skipped during the Trident Protect deletion job, remaining from the original namespace.
  • DeploymentConfig objects are copied to the destination cluster, but the ReplicationController is not restored, leaving is up to the deployment to create a new one with undefined Secret references, causing the VM not to boot on the destination.
  • When using the Openshift image registry, ImageStream and related objects (ImageTag and ImageStreamTag) are deleted, causing ImagePullBackoff issues on recovery when failed back.

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.