Scheduling OpenShift Monitoring in different nodes including tainted ones

Issue

• OpenShift Monitoring pods cannot be scheduled in different nodes.
• OpenShift Monitoring pods cannot be scheduled in tainted nodes even if tolerations have been defined in the configuration.

• OpenShift Monitoring failing to be scheduled:

  Warning   FailedScheduling         pod/thanos-querier-xxxxxxxx-xxxxx                            0/X nodes are available: Y node(s) didn't match Pod's node affinity/selector, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, Z node(s) had untolerated taint {node.ocs.openshift.io/storage: true}. preemption: 0/X nodes are available: X Preemption is not helpful for scheduling.
  

  Warning   FailedScheduling    pod/prometheus-operator-xxxxxxxx-xxxxx                      0/X nodes are available: Y node(s) didn't match Pod's node affinity/selector, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/X nodes are available: X Preemption is not helpful for scheduling.