Skip to main content
NetApp Knowledge Base

Openshift upgrade may cause trident-controller to not start anymore

Views:
Visibility:
Public
Votes:
0
Category:
trident-openshift
Specialty:
snapx
Last Updated:

Applies to

  • Trident for Openshift (25.06.1)
  • Openshift upgrade from 4.17.35 to 4.17.38

Issue

After the upgrade, and trident PODs restarts, the trident-controller does not come online.
Any and all volume operations will stop functioning, since they all go through the trident-controller main container.
 
The following error is seen from the daemonset:
Type            Status      Updated                 Reason                      Message
---------------------------------------------------------------------------------------------------
Available       False       Sep 9, 2025, 2:57 PM    MinimumReplicasUnavailable  Deployment does not have minimum availability
---------------------------------------------------------------------------------------------------
ReplicaFailure  True        Sep 9, 2025, 2:57 PM    FailedCreate            pods "trident-node-linux-" is forbidden: unable to validate against any security context constraint: spec.volumes[10]: Invalid value: "secret": secret volumes are not allowed to be used.
---------------------------------------------------------------------------------------------------

 

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.