Users can not schedule the network-check-source pod in openshift-network-diagnostics namespace

Issue

Since OCP4.7 network connection health checks performed by controllers in openshift-network-diagnostics namespace.
However, this is not working normally in OCP clusters having worker nodes in separated networks.
Because network-check-source pod deployed in any nodes randomly. So, if the pod is running on a network isolated worker node, podnetworkconnectivitycheck doesn't be created normally. the pod should be scheduled on a node that communicates to every node.
But, users can't schedule network-check-source pod to a specific node.