Openshift upgrade may cause trident-controller to not start anymore
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.
---------------------------------------------------------------------------------------------------