Applies to Netapp Astra Trident RedHat Enterprise Linux (RHEL) 8.6 Issue In a Trident deployment, several Trident pods got stuck in CrashLoopBackOff status: kubectl get pods -n trident NAME READY STAT...Applies to Netapp Astra Trident RedHat Enterprise Linux (RHEL) 8.6 Issue In a Trident deployment, several Trident pods got stuck in CrashLoopBackOff status: kubectl get pods -n trident NAME READY STATUS trident-controller-xxxx-yyy 6/6 Running trident-node-linux-xyxyx 0/2 CrashLoopBackOff trident-node-linux-yzyzx 0/2 CrashLoopBackOff trident-node-linux-xzxzz 0/2 CrashLoopBackOff trident-operator-xxxxx-ffff 1/1 Running