Skip to main content
NetApp Knowledge Base

Trident not preserving existing annotations after update from v26.02.0 to v26.02.1

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
astra_trident
Specialty:
snapx
Last Updated:

Applies to

  • AFF-C800
  • 9.16.1P5 CLUSTER-MODE
  • Trident 26.02.1
  • OpenShift

Issue

After upgrading Trident Operator from version v26.02.0 to v26.02.1 on the Kubernetes cluster MSPWST01, the annotation defined in the trident-controller deployment was not preserved. This required a manual update to the deployment and restarting all related pods. The issue was first observed on the day of the upgrade and has occurred during previous upgrade events as well. Only the Trident upgrade was performed, and no other environmental changes were reported.

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.