Replica allocation after Node is DisabledScheduling

[brickpattern]

Q - Similar to Kubectl Cordon that disables a pod scheduling on that node, is there equivalent of that for the Solr Operator?

1. The solrcloud-n pod is already active and alloted with certain core/replica on it. How to prevent further core/replica allocation on that pod?
2. when hitting SPLITSHARD via api, how to prevent that core/replica from going into solrcloud-n pod.
3. when solr core/replica was filling up , had to manually Rebalance by hitting REBALANCEAPI . should operator be automatically moving the core/replica to another available pod?

[HoustonPutman]

This is something that would also have to be implemented in Solr, not just the Solr Operator, because there is no mechanism currently to "cordon-off" nodes when placing replicas.