Dynamic way of scheduling trident pod(s) for multiple tainted nodes.

[Pravinkumar-netapp]

Dynamic way of scheduling trident pod(s) for multiple tainted nodes.
We would like to have trident version that will respect taint effect and operator rather taint key,operator.

• How big is your cluster?
Ans: trident has been installed on multiple cluster (6+) and total no of node(s) are 650+
• Issue with current version?
Ans: Yes. Trident v23 (23.0.1)
• Give us brief explanation the logic ?
Ans: In our environment, Taint of node may vary over time. So we would like to have trident configuration such that trident pod(s) gets scheduled dynamically.
For example: we have a taint on a node as test=taint1:NoSchedule. And we would like to have the trident configuration such that its takes effect (NoSchedule) only and able to tolerate.